Skip to main content
Glama

Search parliamentary business

search_parliament_business
Read-only

Search Curia Vista for federal parliamentary business by title keyword to find motions, postulates, interpellations and bills with number, type, status and submission date.

Instructions

Search Curia Vista for federal parliamentary business (motions, postulates, interpellations, bills) by title keyword (case-insensitive). Returns business number, type, status and submission date.

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": {
      "query": "<query>"
    },
    "name": "search_parliament_business"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesKeyword to search in business titles, e.g. 'Klimaschutz', 'AI'
languageNoLanguage of titles searched (DE has best coverage)DE

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.8/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 genuine behavioral context beyond that: the case-insensitive matching rule and the four returned fields ('business number, type, status and submission date'), which matters because there is no output schema. It stops short of disclosing truncation/pagination behavior for the limit parameter or how result ordering works.

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?

Two sentences with zero filler: the first states the operation, corpus, matching rule, and entity types; the second states exactly what comes back. Front-loaded and appropriately sized for a three-parameter search tool.

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 usefully compensates by listing the returned fields, and it identifies the source corpus and matching semantics. The remaining gap is the limit parameter's effect on result volume and whether results are ranked or paged, which an agent might need to call it confidently at scale.

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 67%, so the baseline is 3. The description reinforces that the keyword applies to titles rather than full text, which is helpful, but it adds nothing about the limit cap or about the language enum's coverage trade-off (only the schema notes 'DE has best coverage'), so neither parameter gains meaning from the description.

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?

Specific verb (search) plus resource (Curia Vista federal parliamentary business), with the covered business types enumerated and the searched field named ('by title keyword (case-insensitive)'). The word 'federal' implicitly separates it from search_local_parliament_business, so an agent can distinguish it from the local sibling without opening a schema.

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 by 'federal parliamentary business' and the title-keyword restriction, which tells the agent this is a keyword lookup rather than a retrieval-by-id operation. However, no sibling is named as an alternative and there is no explicit when-not-to-use statement (e.g., use get_parliament_business for a known business number).

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