Skip to main content
Glama

Find cantonal/municipal parliaments

search_local_parliaments
Read-only

Find Swiss cantons, cities, or municipalities in OpenParlData and check whether their parliament is covered, returning the body_key needed for related local-politics tools.

Instructions

Find Swiss cantons, cities and municipalities in OpenParlData and whether their parliament is covered; returns the body_key used by the other local-politics tools. Example: {query: 'Winterthur'} or {canton: 'BE', with_parliament: true}.

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_parliaments"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNode
typeNo
limitNo
queryNoName of a canton, city or municipality
cantonNoOnly bodies in this canton
with_parliamentNoOnly bodies whose parliament data is covered

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful behavior beyond that: results report whether a parliament is covered, the payload carries a body_key consumable by other tools, and the example with_parliament:true implies a coverage filter, though default result limits and ordering are not mentioned.

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?

One compact sentence covering purpose, scope, and return contract, followed by two example invocations that immediately demonstrate how to call it. Front-loaded and waste-free, though the examples could be introduced more explicitly as opt-in patterns.

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

Completeness4/5

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

With no output schema, the description correctly compensates by stating what comes back (coverage flag plus body_key). Remaining gaps are minor: it does not say that all six parameters are optional so an unfiltered call enumerates everything, nor what the default limit of 25 implies.

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 50%, and the description illustrates two of six parameters (query, canton) plus indirectly with_parliament. It adds usage examples but leaves lang, type, and limit entirely to the schema, so it neither fully compensates for the coverage gap nor adds syntax-level 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?

Names a specific verb (find) and resource (Swiss cantons, cities and municipalities in OpenParlData), and states the output that matters (the body_key used by other local-politics tools). This distinguishes it from siblings like search_local_parliament_business or search_local_politicians, which operate on data rather than resolving bodies.

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

Usage Guidelines4/5

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

The clause 'returns the body_key used by the other local-politics tools' effectively signals this is a discovery/prerequisite step before the other local-politics tools, and two concrete call patterns are given. It stops short of explicitly naming an alternative or stating when not to use it.

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