UK Due Diligence

Overview Schema Source Related Servers Discussions Admin

Get Charity Profile

charity_profile

Read-onlyIdempotent

Retrieve a charity's full Charity Commission profile by registration number, covering trustees, income, expenditure, insolvency flags, classifications, and countries of operation.

Instructions

Fetch the full Charity Commission profile for a charity number.

Returns trustees, latest income/expenditure, insolvency flags, governing document type, classifications, and countries of operation. Use charity_search first to find the charity number.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`charity_number`	Yes	Charity Commission registration number (e.g. '1234567'). Returned by charity_search.

Output Schema

TableJSON Schema

Name	Required	Description
`address`	No	Registered address of the charity (joined address lines).
`insolvent`	No	True if the charity is flagged as insolvent.
`reg_status`	No	Registration status code ('R', 'RM').
`charity_name`	No	Registered charity name.
`charity_type`	No	Charity type.
`latest_income`	No	Latest filed annual income in GBP.
`trustee_names`	No	Trustees on record. Truncated to 30 entries.
`charity_number`	Yes	Charity registration number.
`who_what_where`	No	Who/What/Where classification entries. The list may be truncated truncated to 50 entries.
`reg_status_label`	No	Human-readable registration status.
`in_administration`	No	True if the charity is in administration.
`latest_expenditure`	No	Latest filed annual expenditure in GBP.
`trustee_names_total`	No	Total trustees upstream before truncation.
`date_of_registration`	No	Date of first registration.
`who_what_where_total`	No	Total classification entries upstream before truncation.
`charity_co_reg_number`	No	Companies House number for charities also registered as companies (Charitable Incorporated Organisations, etc.).
`countries_of_operation`	No	Countries the charity operates in (capped at 10 upstream).
`trustee_names_truncated`	No	True if the trustee list was truncated.
`who_what_where_truncated`	No	True if the classification list was truncated.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.0.6May 2, 2026
Removedv1.0.1May 1, 2026
First observedv1.0.0Apr 29, 2026

TDQS

A4.5/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, non-destructive, and idempotent. The description adds meaningful behavioral context about what data to expect (trustees, income/expenditure, insolvency flags) and that it returns a 'full' profile. This goes beyond the annotations without contradicting them.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the core action, and no filler. The second sentence efficiently lists return contents. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple one-parameter schema and availability of an output schema, the description covers the essential context: what it fetches, what it returns, and the prerequisite step. No significant gaps remain.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the parameter description already explains the format and origin ('Returned by charity_search'). The tool description reinforces the usage but doesn't add new meaning beyond the schema beyond implying the parameter is central to the lookup.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses the specific verb 'Fetch' with a clear resource ('full Charity Commission profile') and the input parameter ('charity number'). It lists concrete data fields returned (trustees, income/expenditure, insolvency flags, etc.), which distinguishes this from sibling tools like charity_search or company_profile.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly instructs to use charity_search first to obtain the charity number, which is a clear prerequisite and aligns with the sibling tool. This tells the agent when to use this tool versus the search alternative.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server