Skip to main content
Glama

Cantonal/municipal politicians

search_local_politicians
Read-only

Search cantonal and municipal parliament members by name, optionally within one parliament, and get party, electoral district, and occupation details.

Instructions

Find members of cantonal and municipal parliaments by name, optionally in one parliament: party, electoral district, occupation. Example: {query: 'Meier', body_key: 'ZH'}.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_local_politicians"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNode
limitNo
queryNoName or part of it
offsetNo
body_keyNoParliament: canton code ('ZH', 'VD') or BFS municipality number ('261' = City of Zürich); see search_local_parliaments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the read-only nature is covered. The description's real contribution is enumerating the returned fields (party, electoral district, occupation), which matters because there is no output schema. It says nothing about result limits, pagination, or how partial-name matching behaves, which is a meaningful gap given limit/offset parameters.

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?

Two short sentences with the purpose front-loaded, followed by a concrete example — no filler. The field list ('party, electoral district, occupation') is slightly ambiguous as to whether it describes returns or filters, which costs a point.

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 5-parameter search tool with 40% schema coverage and no output schema, the description supplies the return-field list and one worked example but leaves language, paging, and result-size behavior undocumented. An agent can call it correctly for the common case but must guess at pagination and language handling.

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 only 40%, so the description must carry weight; it does partially by clarifying that body_key scopes to 'one parliament' and by showing query and body_key together in the example. However, lang, limit, and offset receive no explanation in either place, and the body_key format detail (canton code vs. BFS number) lives in the schema, not the description.

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?

States a specific verb and resource ('Find members of cantonal and municipal parliaments') plus scope ('by name, optionally in one parliament'), which is enough to distinguish it from the sibling search_local_parliaments tool that returns the parliaments themselves. It stops short of explicitly naming that sibling in the description, leaving the distinction partly inferential.

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?

The phrase 'optionally in one parliament' implies the two usage modes (broad name search vs. narrowing to a single body) and the example demonstrates the narrow case. There is no explicit when-to-use/when-not guidance or named alternative for related questions.

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