Skip to main content
Glama
bundesregierung-mcp

bundesregierung-mcp

breg_press_releases

Retrieve German federal government press releases in reverse chronological order with page and limit controls to browse current official announcements.

Instructions

Latest press releases (Pressemitteilungen) of the German federal government, newest first. 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, publish time and — for press releases — no description (the teasers carry title + date only).

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

Input Schema

NameRequiredDescriptionDefault
pageNo
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/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. It does well on pagination and ordering and honestly flags a non-obvious trait — press-release items carry no description field, only title and date — but says nothing about auth, rate limits, total result counts, or what happens past the last page.

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 compact sentences, front-loaded with what the tool returns before pagination details. The trailing em-dash aside about missing descriptions is slightly awkward but carries genuine information and nothing is redundant.

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?

With an output schema present, return-field enumeration is optional, yet the description summarizes the item shape anyway and flags the missing description field. Combined with pagination bounds and defaults, an agent has everything it needs to call this correctly.

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

Parameters4/5

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

Schema coverage is 0%, so the description must compensate, and it does: it supplies the limit range 1..50 (absent from the bare integer schema), the default of 10, and that page is 1-based with default 1. That is real meaning beyond the schema's untyped integers.

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 states a specific resource and scope: 'Latest press releases (Pressemitteilungen) of the German federal government, newest first.' An agent knows exactly what it returns and the ordering, though it never distinguishes itself from siblings such as breg_articles or breg_search.

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 the 'latest ... newest first' framing, and it usefully points to breg_get_document as the follow-up for the per-document link. However, there is no explicit statement of when to choose this over breg_articles, breg_health, or breg_search, so routing between list tools is left to inference.

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