> For the complete documentation index, see [llms.txt](https://help.tahua.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tahua.io/product-news/2026/september/admin-read-mcp-delivery.md).

# Contracts, milestones and payments read access in tenant admin MCP

## What it does

The hosted read-only admin MCP (`tahua-admin-read`) covered the pre-award pipeline — funding rounds, applications, applicants, assessments, and the funding decision — but nothing about **grant delivery**: the contract that follows an accepted offer, the milestones/deliverables under it, and the payments made against them.

This adds read access to all three, so a connected assistant can answer questions like "what's contracted for this round", "which milestones are due or approved", and "what's been paid".

## What's new

Six new read-only tools:

* **`list_contracts`** / **`get_contract`** — contracts, filterable by funding round, application, applicant, or state.
* **`list_milestones`** / **`get_milestone`** — deliverable milestones, filterable by funding round, application, contract, or state.
* **`list_payments`** / **`get_payment`** — payments, filterable by funding round, application, milestone, or state.

### What each summary contains

* **Contract** — title, state, amount, start/end dates, contract number, contract manager, whether it's a variation, milestone count, and references to the application / funding round / applicant.
* **Milestone** — title, description, type, funding amount (and estimated amount / amount type), due date, state, paid status and date, submitted/published dates, and references to the application / contract / funding round / applicant.
* **Payment** — amount, state, paid date, payment category, batch id, and references to the milestone / application / funding round / applicant.

### Notable boundaries

* **Milestones are filtered to deliverables** — decision *conditions* (which are also milestone records internally) are excluded here; they already appear in `get_application_context`'s decision object.
* **Summary only** — no contract/letter documents or snapshots, no raw deliverable form answers, **no bank account numbers**, and **no external accounting identifiers** (Xero / QuickBooks / MYOB / Accredo bill and payment ids). Monetary amounts are returned as numbers.

## Security and scoping

Contracts, milestones, and payments are all CanCan data-policy subject classes, so each tool scopes with the same `in_org(organisation).accessible_by(ability, :read)` recipe as the rest of the MCP. An administrator only sees delivery records for funding rounds their data policy permits. No new permissions are introduced.

## UI changes

None. This is an API/MCP capability only.
