Openparliament Ca

List Politicians

list_politicians

Read-onlyIdempotent

Current + historic MPs.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "party": "liberal",
      "current": true
    },
    "name": "list_politicians"
  }
}

Input Schema

Name	Required	Description
`name`	No	Name fragment
`limit`	No
`party`	No	Party slug
`offset`	No
`current`	No	Only currently sitting (default true)
`province`	No	Province code (e.g. "ON")

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "current": true,
+    "party": "liberal"
+  },
+  {
+    "limit": 20,
+    "name": "Smith",
+    "province": "ON"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "List of current and historic Members of Parliament with pagination",
+  "type": "object"
+}

First observedMay 13, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint, covering safety and mutability. The description adds that it returns 'current + historic' MPs, which is a useful behavioral detail not in annotations. It does not contradict annotations.

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, highly concise with no redundant information. However, it may be too terse—it does not elaborate on important aspects like pagination or default filters. It earns its place by stating the core function but could be slightly more informative.

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?

Given the presence of 6 optional parameters and an output schema, the description does not explain pagination (limit, offset) or default filtering behavior. It is minimally complete but lacks details that would help an agent use the tool effectively without relying on the schema alone.

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 coverage is 67%; some parameters (limit, offset) lack descriptions. The description does not explain parameters beyond what the schema provides. For parameters with descriptions (name, party, current, province), the tool description adds no extra meaning, so the baseline score of 3 applies.

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 'Current + historic MPs' clearly indicates the resource (MPs) and scope (current and historic), distinguishing it from single-item tools like get_politician and other listing tools. However, it omits an explicit verb like 'list', relying on the tool name, which slightly reduces clarity.

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 provided on when to use this tool versus alternatives such as get_politician, search_debates, or list_bills. The description lacks any context for when this tool is appropriate or when to prefer other tools.

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

All Openparliament Ca 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.