Skip to main content
Glama
paulieb89

UK Legal Research MCP Server

by paulieb89
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

Get Member Financial Interests

parliament_member_interests
Read-onlyIdempotent

Retrieve UK MP and peer financial interest declarations by member ID. Filter by category (donations, directorships, land, gifts) and paginate for comprehensive results.

Instructions

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
NameRequiredDescriptionDefault
member_idYesParliament Members API integer ID. Get from parliament_find_member.
categoryNoFilter 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.
offsetNoNumber 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.
limitNoMax 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.
max_description_charsNoPer-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
NameRequiredDescriptionDefault
member_idYesParliament Members API member ID
categoryNoCategory filter applied to this query, or None for all categories
offsetYesNumber of interests skipped before this page
limitYesMax interests requested for this page
returnedYesNumber of interests actually returned in this call
has_moreYesTrue if there may be more interests beyond this page. Re-call with offset=offset+returned to fetch the next page.
interestsNoThe interests in this page. `description` text is capped per the max_description_chars input parameter.

Tool Definition Quality

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true. Description adds critical details: hard cap on limit (verified live), pagination logic, and max_description_chars. Could mention rate limits but not required given context.

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?

Well-structured, front-loaded with use case and prerequisite. Each sentence adds distinct value without redundancy. Appropriate length for the tool's complexity.

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 5 parameters, presence of output schema, and sibling tools, the description fully covers pagination, filtering, limits, and source authority. No gaps remain for agent decision-making.

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 covers all 5 parameters fully (100% coverage). Description adds value by explaining limit cap, pagination mechanism, and purpose of max_description_chars, going beyond schema basics.

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 clearly states 'get their registered financial interests' with specific categories. It distinguishes from siblings by noting it's the authoritative source and referencing the prerequisite parliament_find_member.

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 says 'USE THIS TOOL WHEN you have a member_id and need their registered financial interests.' Provides prerequisite call to parliament_find_member and pagination instructions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/paulieb89/uk-legal-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server