Skip to main content
Glama

Uk Parliament

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Search Hansard

search_hansard
Read-onlyIdempotent

Search debate contributions in Hansard.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skipNo0-based offset
takeNo1-20 (default 20)
houseNoCommons | Lords
queryYesFull-text query
date_toNoYYYY-MM-DD
date_fromNoYYYY-MM-DD
member_idNoFilter by contribution member id

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
ResultsNo
SearchTermsNo
TotalResultCountNo
SpokenResultCountNo
WrittenResultCountNo
DivisionsResultCountNo
CorrectionsResultCountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • addedOutput schema / properties / CorrectionsResultCount
      Added value: +{
+  "type": "number"
+}
    • addedOutput schema / properties / DivisionsResultCount
      Added value: +{
+  "type": "number"
+}
    • addedOutput schema / properties / Results
      Added value: +{
+  "items": {
+    "properties": {
+      "AttributedTo": {
+        "type": "string"
+      },
+      "ContributionExtId": {
+        "type": "string"
+      },
+      "ContributionText": {
+        "type": "string"
+      },
+      "ContributionTextFull": {
+        "type": "string"
+      },
+      "DebateSection": {
+        "type": "string"
+      },
+      "DebateSectionExtId": {
+        "type": "string"
+      },
+      "DebateSectionId": {
+        "type": "number"
+      },
+      "DebateSectionOrder": {
+        "type": "number"
+      },
+      "HRSTag": {
+        "type": "string"
+      },
+      "HansardSection": {
+        "type": "string"
+      },
+      "House": {
+        "type": "string"
+      },
+      "ItemId": {
+        "type": "number"
+      },
+      "MemberId": {
+        "type": "number"
+      },
+      "MemberName": {
+        "type": "string"
+      },
+      "OrderInDebateSection": {
+        "type": "number"
+      },
+      "Rank": {
+        "type": "number"
+      },
+      "Section": {
+        "type": "string"
+      },
+      "SittingDate": {
+        "type": "string"
+      },
+      "Timecode": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / SearchTerms
      Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / SpokenResultCount
      Added value: +{
+  "type": "number"
+}
    • addedOutput schema / properties / TotalResultCount
      Added value: +{
+  "type": "number"
+}
    • addedOutput schema / properties / WrittenResultCount
      Added value: +{
+  "type": "number"
+}
    • removedOutput schema / properties / results
      Removed value: -{
-  "description": "List of matching debate contributions",
-  "items": {
-    "description": "Individual contribution record",
-    "type": "object"
-  },
-  "type": "array"
-}
    • removedOutput schema / properties / totalResults
      Removed value: -{
-  "description": "Total count of matching contributions",
-  "type": "number"
-}
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "house": "Commons",
+    "query": "climate change"
+  },
+  {
+    "date_from": "2024-01-01",
+    "date_to": "2024-12-31",
+    "house": "Lords",
+    "query": "NHS funding",
+    "take": 15
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "Search results for Hansard debate contributions",
+  "properties": {
+    "results": {
+      "description": "List of matching debate contributions",
+      "items": {
+        "description": "Individual contribution record",
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "totalResults": {
+      "description": "Total count of matching contributions",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}
  3. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds no behavioral context such as pagination limits, full-text nature, or that results are sorted by relevance. It merely repeats the verb 'Search' without enriching the agent's understanding of side effects or constraints.

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?

The description is a single short sentence that states the action and resource immediately. It is concise and front-loaded, with no filler words. It could earn a 5 by naming alternatives, but it is suitably compact.

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

Completeness3/5

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

For a tool with 7 parameters, an output schema, and rich annotations, the description is minimal but not misleading. It does not explain the scope of 'debate contributions' or hint at date filtering, but the schema covers all parameters. It is adequate, though an agent might benefit from a brief note on what a 'contribution' is.

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%, so all 7 parameters are documented in the schema. The description adds no additional meaning beyond the schema, which is acceptable per the baseline of 3 when coverage is high.

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

Purpose4/5

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

The description clearly identifies the action ('Search') and the resource ('debate contributions in Hansard'), which is distinct from sibling tools like search_bills and search_members. It does not explicitly name alternatives, but the resource being searched is unambiguous.

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

Usage Guidelines2/5

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

No guidance is given on when to use this tool versus alternatives like search_bills, search_members, or search_within. The description only states what the tool does, leaving the agent to infer appropriate use from the tool name and schema.

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

All Uk Parliament 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