Skip to main content
Glama
bundesregierung-mcp

bundesregierung-mcp

breg_get_document

Retrieve the full text and metadata of a bundesregierung.de press release, article, or speech from its URL, including the official English translation when available.

Instructions

Full text of one bundesregierung.de document — a press release, article or speech/transcript. url: a www.bundesregierung.de document URL, e.g. from breg_press_releases (/breg-de/aktuelles/pressemitteilungen/...) or a /breg-de/suche/- alias from breg_search (it redirects to the canonical document). Returns title, publish time, kind (press-release / article / speech / document), the German body text and its word count, plus body_en with the official English translation when the site carries one inline (has_english_translation). Speech pages carry no machine-readable publish time — their date is read from the header's German date line when present. Nothing is ever fabricated.

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": {
      "url": "<url>"
    },
    "name": "breg_get_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses the returned fields, the kind enumeration, inline English translation availability, and the speech-page quirk where publish time is absent or read from a German date line. The "nothing is ever fabricated" note is a useful data-integrity signal. Failure behavior for a non-document or off-domain URL is not covered.

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 purpose, then URL guidance, then return shape; each block is informative. Slightly dense with stacked parentheticals, but nothing is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-URL fetch tool with one required param, the definition covers sourcing the input, canonicalization via redirect, return shape and known data caveats. An output schema exists, so the return-field listing is light overlap rather than a gap.

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 coverage is 0% - the schema only says url is a string - so the description must compensate, and it does: it constrains the domain, shows concrete path shapes, explains the search-alias redirect form, and implies one URL per call. That is meaning well beyond the schema.

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?

Opens with a specific verb+resource+scope: "Full text of one bundesregierung.de document", then enumerates the content kinds (press release, article, speech/transcript). It explicitly separates itself from breg_press_releases and breg_search by defining them as URL sources rather than competitors.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tells the agent exactly where to obtain the required url - from breg_press_releases paths or a /breg-de/suche/<slug>-<id> alias from breg_search - and notes that alias redirects to the canonical document. It stops short of an explicit when-not-to-use statement, but the retrieval-then-fetch workflow is unambiguous.

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