Skip to main content
Glama

Cantonal/municipal business details

get_local_parliament_business
Read-only

Retrieve a cantonal or municipal parliamentary business item by ID to view its title, type, status, dates, authors, documents, and votes.

Instructions

One item of cantonal/municipal parliamentary business by id: title, type, status, dates, authors (contributors), documents and votes where available.

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": {
      "id": "<id>"
    },
    "name": "get_local_parliament_business"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesBusiness id from search_local_parliament_business
langNode

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.5/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 safety profile is covered. The description adds useful context about the payload shape and the 'where available' caveat that some sub-resources (documents, votes) may be absent, but says nothing about permissions, error behavior for bad ids, or localization effects.

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?

A single front-loaded sentence with no filler; the field list is dense but each item tells the agent what to expect in the response. Slightly list-heavy but nothing is wasted.

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?

For a simple two-parameter read tool with no output schema, describing the returned fields and the 'where available' caveat is nearly sufficient. The only meaningful omission is clarifying what lang affects in the response.

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 50%: the id parameter is well documented in the schema with its provenance, but the lang parameter (enum de/fr/it/en, default de) has no description in either place. The description does not compensate by explaining that lang controls the language of the returned content, which is the main semantic gap.

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 uses a clear retrieval-by-id framing and enumerates exactly what an item contains (title, type, status, dates, authors, documents, votes). The 'by id' scope implicitly contrasts with the sibling search_local_parliament_business, though it never names that sibling to make the distinction explicit.

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?

Usage is implied: fetch one business record when you already have an id (the schema notes the id comes from search_local_parliament_business). There is no explicit statement of when to prefer this over search tools or what to do when the id is unknown, so guidance remains inferential.

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