Skip to main content
Glama

ParliamentOS – Bundestag, Landtage, Nationalrat, EU

Quellen suchen

search
Read-onlyIdempotent

Sucht parlamentarische Quellen zu einem Thema: Reden aus Bundestag, Landtagen, Nationalrat und EU-Parlament sowie Bundestagsdrucksachen. Gibt je Treffer id, title, text, url (Beleg-Seite von ParliamentOS) und original_url (amtliches Originaldokument, wo die Quelle eines führt) zurück; die id öffnet das Werkzeug fetch. Nenne je Treffer beide Links. [Ohne KI: liefert ausschließlich Originaldaten aus amtlichen Quellen.]

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

Input Schema

NameRequiredDescriptionDefault
queryYesSuchbegriff oder Thema, z. B. 'Mietpreisbremse'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile needs no restating. The description adds genuinely new behavioral context: the exact return fields (id, title, text, url, original_url), what each URL represents, the id-to-fetch handoff, and a usage instruction to cite both links per hit. It omits result limits, pagination and ranking behavior, which keeps it from a 5.

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?

Two tightly packed sentences that front-load the scope, then the return shape, then the fetch handoff and citation rule — each sentence carries operational information. The trailing bracketed line about non-AI delivery of official source data is mildly promotional and not needed by an agent, a minor deduct.

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 and a single parameter, the description carries the return-value burden itself and does so well, listing all five fields and their meanings. It is nearly complete for this complexity; the missing pieces are retrieval mechanics an agent may need — result caps, pagination, or how relevance is ordered.

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?

Only one parameter exists with 100% schema description coverage, so the schema already documents 'query' as 'Suchbegriff oder Thema' with a worked example ('Mietpreisbremse'). The description adds no further syntax, operator or matching-mode information, so the baseline 3 applies.

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 names a concrete verb and resource ('Sucht parlamentarische Quellen zu einem Thema') and enumerates the exact corpora covered — Bundestag, Landtage, Nationalrat, EU-Parlament and Bundestagsdrucksachen — so an agent understands this is a broad cross-parliament search, not a single-source one. It falls short of 5 because it never explicitly contrasts itself with the many source-specific siblings (search_speeches, search_drucksachen, etc.), leaving the distinction implicit.

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 rather than stated: the broad source list suggests 'use this when you want an unfiltered topical sweep across parliaments,' and the note that 'die id öffnet das Werkzeug fetch' gives a clear follow-up path. There is no explicit when-not guidance or named alternative for narrow searches, so an agent with 20+ sibling search tools must infer the routing itself.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.