> 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-application-decisions.md).

# Application funding decision in tenant admin MCP context

## What it does

The hosted read-only admin MCP (`tahua-admin-read`) lets a connected AI assistant answer questions about an organisation's funding data. It could already report an application's assessments and pipeline state, but not the **funding decision** — whether the application was approved or declined, the amount offered, any conditions attached, and whether the applicant accepted or declined the offer.

This adds the funding decision to the application context.

## What's new

`get_application_context` now returns a **`decision`** object alongside the existing application, funding round, applicant, assessments, and final assessment score. It is `null` when the application has no decision yet.

The `decision` object contains:

* **`decision`**, **`approved`**, **`declined`** — the outcome (approved/declined).
* **`state`** — where the decision is in its lifecycle (draft → review → sent).
* **`sent`** / **`sent_at`** — whether the decision letter has been sent to the applicant, and when.
* **`notification_choice`** / **`auto_accept`** — whether the offer auto-accepts or requires the applicant to accept/decline.
* **`amount_granted`** — the amount offered to *this* application.
* **`conditions`** — any conditions attached to the decision (id, title, funding amount, due date).
* **`accepted_at`** / **`declined_at`** — when the applicant accepted or declined the offer.
* **`title`** and timestamps.

No new tools are added — the decision is deliberately part of the application context rather than a standalone endpoint.

## Security and scoping

The decision is only ever returned for an application the administrator can already read (`get_application_context` runs on the tenant- and data-policy-scoped set of applications). It exposes only *that application's* own offer amount — never the other applications in a batch decision — so nothing is revealed beyond the administrator's data policy. No new permissions are introduced.

## What it deliberately does not expose

Consistent with the rest of this MCP, the decision is a **summary**: it does **not** include the organisation-defined custom decision fields, the free-text applicant notification message, or the raw letter-of-offer document. Those can be added later as a deliberate scope extension.

## UI changes

None. This is an API/MCP capability only.
