Skip to main content
Glama

search_parliament_speeches

Read-onlyIdempotent

Retrieves debate speeches for a parliamentary affair from an OpenParlData affair ID, with an optional result limit.

Instructions

Debate speeches on a parliamentary affair

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "affair_id": "<affair_id>"
    },
    "name": "search_parliament_speeches"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNomax 20
affair_idYesOpenParlData affair ID (from search_parliament_business)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.9.0
    • changedInput schema / properties / affair_id / description
      Previous value: -"OpenParlData affair ID (get from search_parliament_business results)"New value: +"OpenParlData affair ID (from search_parliament_business)"
    • addedInput schema / properties / limit / default
      Added value: +5
    • changedInput schema / properties / limit / description
      Previous value: -"Max speeches to return (default: 5, max: 20)"New value: +"max 20"
  2. First observed

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that: no indication of ordering, whether all speeches for the affair are returned, how limit truncates results, or what a speech entry contains.

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

Conciseness3/5

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

It is short with zero waste, but it is a sentence fragment rather than a front-loaded sentence, and its brevity comes from under-specification rather than efficient editing. There is no structure to guide an agent reading it quickly.

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

Completeness2/5

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

For a simple two-parameter read tool with no output schema, the description still should say what is returned and how results are ordered or truncated. As written, an agent knows only the resource domain, not the shape or behavior of the response.

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 affair_id explaining its source tool and limit documenting a max of 20, so the schema does the heavy lifting. The description contributes no additional parameter meaning, which fits the baseline of 3 for fully documented schemas.

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

Purpose2/5

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

The description is a noun fragment, 'Debate speeches on a parliamentary affair,' with no verb indicating retrieval, listing, or search behavior. It largely restates the tool name (search_parliament_speeches) plus the affair scoping, and gives no basis for distinguishing it from siblings like get_parliament_votes or search_parliament_business.

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?

There is no when-to-use guidance, no mention of alternatives, and no prerequisites. The only workflow hint - that affair_id comes from search_parliament_business - lives in the schema, not the description, so the description itself offers no routing help.

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

Deploy Server

Other Tools