Skip to main content
Glama

Openparliament Ca

by io.github.pipeworx-io

Search Debates

search_debates
Read-onlyIdempotent

List Hansard speeches (debate contributions) by a specific MP and/or party, optionally within a date range. Returns who spoke, when, and the speech text. IMPORTANT: the OpenParliament API has NO free-text/topic search — you must filter by politician (MP slug; find one via list_politicians) and/or party. There is no way to search debates by subject keyword.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo1-100 (default 20)
partyNoParty slug (e.g. "liberal", "conservative", "ndp")
offsetNo0-based offset
date_toNoYYYY-MM-DD
date_fromNoYYYY-MM-DD
politicianNoMP slug, e.g. "justin-trudeau" (use list_politicians to find slugs)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed5 schema fields changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "query": "climate change"
-  },
-  {
-    "date_from": "2023-01-01",
-    "date_to": "2023-12-31",
-    "limit": 50,
-    "party": "liberal",
-    "query": "healthcare funding"
-  }
-]New value: +[
+  {
+    "limit": 10,
+    "politician": "justin-trudeau"
+  },
+  {
+    "date_from": "2024-01-01",
+    "date_to": "2024-12-31",
+    "limit": 50,
+    "party": "liberal"
+  }
+]
    • changedInput schema / properties / party / description
      Previous value: -"Party slug (e.g. \"liberal\", \"conservative\")"New value: +"Party slug (e.g. \"liberal\", \"conservative\", \"ndp\")"
    • changedInput schema / properties / politician / description
      Previous value: -"Politician slug"New value: +"MP slug, e.g. \"justin-trudeau\" (use list_politicians to find slugs)"
    • removedInput schema / properties / query
      Removed value: -{
-  "description": "Full-text query",
-  "type": "string"
-}
    • removedInput schema / required
      Removed value: -[
-  "query"
-]
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "climate change"
+  },
+  {
+    "date_from": "2023-01-01",
+    "date_to": "2023-12-31",
+    "limit": 50,
+    "party": "liberal",
+    "query": "healthcare funding"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "Search results from Hansard contributions (debates)",
+  "type": "object"
+}
  3. First observed

TDQS

A4.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds context about return fields and API limitations, but does not disclose any additional behavioral traits beyond what annotations provide.

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?

Three concise, front-loaded sentences. Each sentence adds value: purpose, limitation, and filter requirement. No wasted words.

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 6 parameters, no required params, 100% schema coverage, output schema presence, and comprehensive annotations, the description is complete. It explains what to do, what not to do, and includes examples in the schema.

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 coverage is 100%, but the description adds practical usage notes like date format, offset base, and how to obtain politician slugs via list_politicians, enhancing schema meaning.

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 the tool lists Hansard speeches by MP and/or party, optionally filtered by date, and returns speaker, date, and text. It distinguishes from siblings like list_politicians.

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 states the API has no free-text search and requires filtering by politician or party. Provides guidance on finding politician slugs via list_politicians.

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

All Openparliament Ca toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.1/5.0
Disambiguation2/5

The tool set mixes two distinct domains: 8 Canadian Parliament tools and 30 Pipeworx data tools. Within each domain, tools are somewhat distinct, but the overall mix creates confusion as agents cannot tell if a tool is for parliament or general data lookup.

Naming Consistency2/5

OpenParliament tools follow a consistent verb_noun pattern (list_*, get_*), but Pipeworx tools use varied conventions (e.g., 'remember', 'discover_tools', 'ask_pipeworx'). The lack of a unified naming scheme across the set reduces predictability.

Tool Count2/5

38 tools is excessive for a Canadian Parliament server. The core parliament tools (8) are well-scoped, but the addition of 30 unrelated Pipeworx tools makes the count bloated and inappropriate for the stated domain.

Completeness1/5

For the Canadian Parliament domain, coverage is adequate but lacks topic search and detailed legislative history. However, the server is dominated by Pipeworx tools, which are out of scope, making the overall surface severely incomplete for the implied purpose.

Resources