Skip to main content
Glama

search_cantonal_affairs

Read-onlyIdempotent

Search affairs in any Swiss cantonal parliament (Kantonsrat) by canton code and optional German query, returning matching items for research and monitoring.

Instructions

Search affairs in a cantonal parliament (Kantonsrat), all 26 cantons

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": {
      "canton": "<canton>"
    },
    "name": "search_cantonal_affairs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNomax 20
queryNoGerman term, e.g. Bildung
cantonYesCanton code, e.g. ZH

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.9.0
    • changedInput schema / properties / canton / description
      Previous value: -"Canton abbreviation: ZH, BE, LU, UR, SZ, OW, NW, GL, ZG, FR, SO, BS, BL, SH, AR, AI, SG, GR, AG, TG, TI, VD, VS, NE, GE, JU"New value: +"Canton code, e.g. ZH"
    • addedInput schema / properties / limit / default
      Added value: +5
    • changedInput schema / properties / limit / description
      Previous value: -"Max results (default: 5, max: 20)"New value: +"max 20"
    • changedInput schema / properties / query / description
      Previous value: -"Search term (optional, e.g. 'Bildung', 'Verkehr')"New value: +"German term, e.g. Bildung"
  2. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare the operation read-only, idempotent, non-destructive, and open-world, so the safety profile is covered. The description adds the cantonal scope, but it does not describe return format, pagination, ordering, or any rate-limit behavior 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?

The description is a single front-loaded sentence with no wasted words: the action, resource, and scope appear immediately. It is appropriately short for a low-complexity, three-parameter search tool.

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 three-parameter search tool with rich annotations and full schema coverage, the definition is minimally complete. However, there is no output schema and the description does not explain what an 'affair' result contains, so an agent lacks return-value context even if invocation mechanics are covered.

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%, so the input schema already documents limit, query, and canton with examples. The description adds no parameter-level meaning such as whether query is optional, how canton codes are matched, or what the default limit returns, so baseline 3 is appropriate.

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 gives a clear verb ('Search') and resource ('affairs in a cantonal parliament'), and scopes it to all 26 cantons. It implicitly distinguishes cantonal parliament affairs from federal-level siblings, but it never names the closest alternative such as 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 explicit guidance about when to use this tool versus the many parliament-related siblings, nor any when-not-to-use condition. The canton requirement is only visible in the schema, and the description does not explain query language behavior or result scope beyond the one-line purpose.

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