Skip to main content
Glama
bundesregierung-mcp

bundesregierung-mcp

breg_search

Search bundesregierung.de by keyword across press releases, articles, and speeches. Use query, limit, and page parameters to find matching documents and their links.

Instructions

Search bundesregierung.de by keyword across the whole site (press releases, articles, speeches). query: free text, e.g. "Klima" or "Bundeshaushalt 2027". limit: 1..50 (default 10); page: 1-based starting page (default 1). Items carry title, topline, link (a /breg-de/suche/ alias URL — breg_get_document follows it to the canonical document), publish time and a short description.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
limitNo
queryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full behavioral burden and does reasonably well: it discloses pagination defaults and bounds (1..50, default 10; 1-based page, default 1) and describes the returned fields, including the non-obvious detail that the link is a /breg-de/suche/ alias URL that breg_get_document resolves to the canonical document. It omits sort/relevance ordering, rate limits, and any auth requirements.

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?

The what-and-where statement is front-loaded and the parameter details follow in a compact clause-per-parameter pattern. The trailing parenthetical about the alias URL is slightly wordy but earns its place by warning about link resolution.

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 an output schema present, the description need not detail return values, yet it still summarizes item fields and paging, which is more than adequate for a 3-parameter search tool. The remaining gap is guidance on choosing among the content-type siblings and on result ordering/relevance.

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%, so the description must compensate, and it does so for all three parameters: query is free text with worked examples, limit has both a range and a default, and page is specified as 1-based with a default. Nothing in the schema is left unexplained.

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?

States a specific verb ('Search'), a specific resource ('bundesregierung.de'), and the scope ('across the whole site'), plus it enumerates the content types covered (press releases, articles, speeches). That site-wide scope implicitly separates it from the content-type-scoped siblings such as breg_articles and breg_press_releases.

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?

The description gives concrete query examples ('Klima', 'Bundeshaushalt 2027') which helps an agent construct a call, but it never states when to prefer this site-wide search over breg_articles, breg_press_releases, or breg_speeches, nor any exclusion conditions. Usage is inferred rather than instructed.

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