Skip to main content
Glama

UK Business Tools - Ledgerhall

by dev.fly.uk-business-mcp
OverviewDiscussionsAdmin

Find Member of Parliament

law_parliament_find_member
Read-onlyIdempotent

USE THIS TOOL WHEN you have a member's name and need their integer member_id.

Returns all members matching the name query, each with the integer id, party, constituency, house, and current-sitting status. Disambiguates common-name matches (e.g. "Lord Smith" returns multiple peers).

CALL THIS BEFORE any tool that filters by member_id — including parliament_get_debate_contributions, parliament_member_debates, and parliament_member_interests. Name → ID first; ID-based filtering second. Skipping this step and text-searching by name returns unrelated results (see parliament_search_hansard's anti-bypass note for the Pannick case).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName or partial name, e.g. 'Starmer', 'Baroness Hale'

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesThe name that was searched
totalYesNumber of members matching the query
membersNoMatching members. Use the integer `id` field from any member to call parliament_member_debates or parliament_member_interests.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedOutput schema / properties / members / items / properties / is_current / anyOf
      Added value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedOutput schema / properties / members / items / properties / is_current / default
      Added value: +null
    • changedOutput schema / properties / members / items / properties / is_current / description
      Previous value: -"Whether the member currently sits"New value: +"Whether the member currently sits, in priority order: (1) the source's own membershipStatus.statusIsActive when membershipStatus is present — authoritative, used directly; (2) False when membershipStatus is null/absent but this record's own membershipEndDate is set — an authoritative end date, not an inference from how other records look; (3) None when neither is available — genuinely indeterminate, not fabricated as True or False. A null membershipStatus is NOT by itself read as 'ended'."
    • removedOutput schema / properties / members / items / properties / is_current / type
      Removed value: -"boolean"
    • changedOutput schema / properties / members / items / required
      Previous value: -[
-  "id",
-  "name",
-  "party",
-  "house",
-  "is_current"
-]New value: +[
+  "id",
+  "name",
+  "party",
+  "house"
+]
  2. Changed3 schema fields changed
    • addedInput schema / properties / name
      Added value: +{
+  "description": "Name or partial name, e.g. 'Starmer', 'Baroness Hale'",
+  "maxLength": 200,
+  "minLength": 2,
+  "type": "string"
+}
    • removedInput schema / properties / params
      Removed value: -{
-  "additionalProperties": false,
-  "description": "FindMemberInput with the name (full or partial).",
-  "properties": {
-    "name": {
-      "description": "Name or partial name, e.g. 'Starmer', 'Baroness Hale'",
-      "maxLength": 200,
-      "minLength": 2,
-      "type": "string"
-    }
-  },
-  "required": [
-    "name"
-  ],
-  "type": "object"
-}
    • changedInput schema / required
      Previous value: -[
-  "params"
-]New value: +[
+  "name"
+]
  3. Added
  4. Removed
  5. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare it as read-only, idempotent, open-world, and non-destructive. The description adds substantial behavioral context beyond annotations: it returns all name matches with id, party, constituency, house, and current-sitting status, and it disambiguates common-name matches such as 'Lord Smith'. It also warns about the consequence of bypassing this lookup.

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 triggering condition and then moves through return shape, disambiguation, and ordering requirements. Every sentence is actionable: the return fields help interpret results, the sibling references establish order of operations, and the anti-bypass warning prevents a known failure mode. There is no redundant restatement of the schema or annotations.

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?

For a one-parameter lookup tool with a full output schema and clear annotations, the description supplies everything an agent needs: purpose, usage timing, return fields, disambiguation behavior, and workflow ordering relative to sibling tools. No important operational detail is missing.

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 description coverage is 100%, and the single parameter's schema already explains that it accepts a name or partial name with examples such as 'Starmer' and 'Baroness Hale'. The description reinforces that this is a name query used to obtain an integer ID, but adds no syntax, formatting, or matching behavior beyond the schema. This is the expected baseline when the schema fully documents parameters.

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 states a precise verb and resource: find a Member of Parliament by name and return their integer member_id. It also distinguishes this from sibling tools by naming ID-filtering tools and explaining that name must be resolved to ID first. An agent can identify the exact purpose without opening the schema.

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?

It explicitly says when to use the tool (when you have a member's name and need their integer member_id) and when not to bypass it (calling ID-filtering tools before this one). It names concrete alternatives such as parliament_get_debate_contributions, parliament_member_debates, and parliament_member_interests, and warns that skipping this step produces unrelated results.

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 toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources