Uk Parliament

Search Members

search_members

Read-onlyIdempotent

Search MPs and Lords by name / party / location / house.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	Search across name fields
`skip`	No	0-based offset
`take`	No	1-20 (default 20)
`house`	No	1 = Commons, 2 = Lords
`party`	No	Party name
`location`	No	Postcode or constituency name
`is_current`	No	Only currently-sitting members (default true)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`members`	No	List of member records matching search criteria
`totalResults`	No	Total count of matching members

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 27, 2026

addedInput schema / examples

Added value: +[
+  {
+    "is_current": true,
+    "name": "Keir Starmer"
+  },
+  {
+    "location": "SW1A 1AA",
+    "party": "Labour",
+    "take": 10
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Search results for MPs and Lords",
+  "properties": {
+    "members": {
+      "description": "List of member records matching search criteria",
+      "items": {
+        "description": "Individual member record",
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "totalResults": {
+      "description": "Total count of matching members",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

First observedMay 13, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations (readOnlyHint, idempotentHint, destructiveHint=false) already convey safety. Description adds searchable field categories but omits that is_current defaults to true and does not detail pagination behavior (skip/take).

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

Conciseness4/5

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

Single sentence efficiently conveys purpose. Could be slightly expanded to mention optionality or defaults without losing conciseness.

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

Completeness4/5

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

Output schema covers return values. With 7 optional params and no required ones, description could clarify behavior when no parameters are provided (e.g., returns all?). Still fairly complete given schema richness.

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% with clear parameter descriptions. The tool description merely lists field categories without adding meaning beyond schema. Baseline 3 is appropriate.

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?

Description clearly states a specific verb ('Search') and resource ('MPs and Lords') with filtering dimensions (name/party/location/house). It distinguishes from siblings like get_member and search_bills by resource type.

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

Usage Guidelines3/5

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

Description provides basic usage context but does not explicitly guide when to use this tool versus alternatives (e.g., get_member for a single member, search_within for other data). No when-not or alternative mentions.

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

All Uk Parliament tools Inspect

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.