UK Business Tools - Ledgerhall

Get Member Financial Interests

law_parliament_member_interests

Read-onlyIdempotent

USE THIS TOOL WHEN you have a member_id and need their registered financial interests (donations, directorships, land, gifts).

CALL parliament_find_member(name) FIRST to obtain the integer member_id.

Returns ONE PAGE of interests (default 20, caller controls via limit). For prolific members (big donors, many directorships, extensive land holdings), re-call with offset=offset+returned while has_more is true to paginate. Description text is capped per max_description_chars; raise it for forensic provenance work that needs the full narrative.

This is the authoritative source for UK MP and peer financial-interest declarations (via the Members API). Web search returns stale snapshots.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max interests per call. Hard-capped at 20 by the upstream interests-api.parliament.uk (verified live 2026-05-29: Take=100 still returns 20). For prolific members, paginate via offset; total size is in totalResults on the response.
`offset`	No	Number of interests to skip before this page. Default 0 for the first page. To paginate prolific members (100+ interests), re-call with offset=offset+returned while the previous response had has_more=true.
`category`	No	Filter by interest category. Common categories: 'donations' (donations and support), 'gifts_uk' (gifts/hospitality from UK), 'employment' (employment and earnings), 'land' (land and property), 'shareholdings', 'overseas_visits'. Omit for all categories.
`member_id`	Yes	Parliament Members API integer ID. Get from parliament_find_member.
`max_description_chars`	No	Per-entry cap on the free-text description field. Default 500 prevents context blow-up on members with lengthy donation or directorship narratives. Raise to 2000+ only for forensic provenance work.

Output Schema

TableJSON Schema

Name	Required	Description
`limit`	Yes	Max interests requested for this page
`offset`	Yes	Number of interests skipped before this page
`category`	No	Category filter applied to this query, or None for all categories
`has_more`	Yes	True if there may be more interests beyond this page. Re-call with offset=offset+returned to fetch the next page.
`returned`	Yes	Number of interests actually returned in this call
`interests`	No	The interests in this page. `description` text is capped per the max_description_chars input parameter.
`member_id`	Yes	Parliament Members API member ID

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare readOnlyHint and idempotentHint. The description adds substantial beyond annotations: pagination semantics (one page, default 20, offset pattern), hard-capped limit of 20, per-entry description truncation, and the fact that web search returns stale snapshots. No contradictions.

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?

The description is front-loaded with the use-case trigger, then prerequisite, then pagination, then authority note. Every sentence earns its place; it is detailed yet tightly written with no redundancy.

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?

Covers the main flow (member_id from find_member), pagination for large result sets, parameter limits, description truncation trade-off, and the authoritative source. Given the tool's complexity (5 params, pagination, large result sets), this description is fully adequate.

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

Parameters4/5

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

Schema descriptions cover 100% of parameters with clear meanings (member_id, limit, offset, category, max_description_chars). The description adds pragmatic context on how to use these parameters together, especially the pagination loop and when to raise the character cap. This exceeds the baseline of 3 but does not reinvent the wheel.

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 opens with 'USE THIS TOOL WHEN you have a member_id and need their registered financial interests' – a specific verb+resource+condition. It clearly distinguishes from web search by declaring itself the authoritative API source for MP/peer financial-interest declarations.

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 call parliament_find_member(name) first to obtain the member_id. Provides detailed pagination guidance for prolific members (re-call with offset while has_more is true) and advises raising max_description_chars for forensic work. No ambiguity about when to use.

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

All UK Business Tools - Ledgerhall tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0

Disambiguation4/5

Tools are well-grouped by domain prefixes (dd_, gov_, law_, prop_) with clear descriptions that differentiate them. However, there is minor overlap, e.g., dd_search could be used instead of individual searches, and dd_fetch versus dedicated profile tools might cause confusion.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with domain-specific prefixes (dd_, gov_, law_, prop_). Names are descriptive and predictable, e.g., dd_charity_search, gov_govuk_search, law_bills_search_bills.

Tool Count4/5

70 tools is high but justified by the broad scope covering due diligence, government, legal, and property domains. Each domain has a reasonable number of tools (about 15-20 each). The count is on the upper end but still manageable.

Completeness5/5

The tool set is comprehensive across all domains: full CRUD for companies and charities, detailed legal research (cases, legislation, parliament, citations), property data (EPC, planning, price paid, rentals), and government information. No obvious gaps for the intended use cases.

Resources

Need Help?