Skip to main content
Glama

get_parliamentary_documents

Read-onlyIdempotent

Retrieve official parliamentary documents—reports, committee opinions, Federal Council statements—for a given affair ID to support research on Swiss political affairs.

Instructions

Official documents (reports, committee opinions, Federal Council statements) for a parliamentary affair

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": {
      "affair_id": "<affair_id>"
    },
    "name": "get_parliamentary_documents"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNomax 20
affair_idYesOpenParlData affair ID (from search_parliament_business)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.9.0
    • changedInput schema / properties / affair_id / description
      Previous value: -"OpenParlData affair ID (get from search_parliament_business results)"New value: +"OpenParlData affair ID (from search_parliament_business)"
    • addedInput schema / properties / limit / default
      Added value: +5
    • changedInput schema / properties / limit / description
      Previous value: -"Max documents to return (default: 5, max: 20)"New value: +"max 20"
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds useful context by enumerating the document categories returned, but says nothing about ordering, pagination, empty results, or whether all documents for the affair are returned.

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 tight phrase with zero filler, and the scope qualifier follows immediately after the resource. It is arguably too terse rather than padded, but no sentence is wasted.

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 two-parameter read-only fetch with a fully documented schema and complete annotations, the essentials are covered. However, with no output schema, the returned document structure and pagination behavior are left unexplained beyond the parenthetical examples.

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%, including the crucial note that affair_id comes from search_parliament_business and that limit maxes at 20, so the schema carries parameter meaning. The description only reinforces that the scope is a single parliamentary affair, adding little beyond it.

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?

Names the specific resource (official documents) and scopes it with concrete examples — reports, committee opinions, Federal Council statements — tied to a parliamentary affair. It reads clearly as a fetch-by-affair-ID tool and is distinguishable from siblings like get_parliament_votes or search_parliament_business, though the verb is only implicit.

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?

The description gives no when-to-use guidance and never names the alternative or prerequisite (search_parliament_business to obtain an affair ID) — that hint lives only in the input schema. An agent must infer the workflow entirely.

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