Skip to main content
Glama
bundesregierung-mcp

bundesregierung-mcp

breg_speeches

Retrieve German federal government speeches, press statements, and press conferences with full transcripts, ordered by publication time descending and paginated for browsing.

Instructions

Latest speeches, press statements and press conferences (Pressekonferenzen und Reden) of the German federal government, newest first — mostly full transcripts ("Im Wortlaut"). limit: 1..50 (default 10); page: 1-based starting page (default 1). Items carry title, topline, link (a per-document URL for breg_get_document), type and publish time.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "breg_speeches"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does so reasonably well: it discloses result ordering (newest first), pagination bounds and defaults (limit 1..50 default 10, page 1-based default 1), and the fields each item returns. It omits any statement about total result counts or how to detect the end of pagination, which matters for a paged list tool.

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?

Front-loaded with the resource and ordering, then parameters, then item shape — a sensible order with no filler sentences. The bilingual parenthetical and quoting are slightly noisy but each clause carries information.

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 two-parameter paged list tool with an output schema and no annotations, the description covers ordering, pagination semantics, parameter bounds, and the handoff to breg_get_document. The only missing piece an agent might want is pagination termination behavior, which is minor given the output schema exists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, yet the description fully compensates: it states the valid range for limit (1..50), both defaults (10 and 1), and that page is 1-based. These constraints — especially the 1..50 cap — are not present in the schema at all, so the description adds genuine, call-affecting information.

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 (speeches, press statements, press conferences of the German federal government) and adds useful characterization — 'mostly full transcripts ("Im Wortlaut")' and ordering 'newest first'. It does not explicitly distinguish itself from close siblings like breg_press_releases, so an agent must infer the boundary from the resource nouns alone.

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 tool is for browsing the newest speeches, and the mention that items carry 'a per-document URL for breg_get_document' gives a clear follow-up path to a sibling. There is no explicit when-to-use/when-not guidance versus breg_press_releases or breg_search, which is the main gap.

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