Skip to main content
Glama
bundesregierung-mcp

bundesregierung-mcp

breg_articles

Fetch recent articles and press releases from bundesregierung.de in reverse chronological order, with paging and configurable limits for quick updates.

Instructions

Latest articles / Meldungen from bundesregierung.de, 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), publish time and a short description.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 disclose useful traits: sort order (newest first), hard limit bounds (1..50), default page size, and the shape of returned items. It says nothing about authentication, rate limits, error behavior, or whether the result set is exhaustively paginable, which is a meaningful gap for an unannotated 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?

Compact and front-loaded: the resource and ordering come first, parameter constraints second, return-item contents last. No filler sentences. Slightly run-on in its use of semicolons, but every clause carries information an agent needs.

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 paginated list tool with an output schema present, the description covers purpose, ordering, parameter bounds, and item fields, so return values need not be re-explained. What is missing is relative positioning against the sibling retrieval tools and any indication of total-result or end-of-pagination behavior.

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 description coverage is 0% — the schema only names 'page' and 'limit' with defaults — so the description must compensate, and it largely does: limit is 1..50 with default 10, page is 1-based with default 1. The '1-based' clarification and upper bound are genuinely schema-external information. Minor gap: no guidance on what an out-of-range page returns or when to stop paging.

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?

States a specific verb+resource: 'Latest articles / Meldungen from bundesregierung.de, newest first', which tells an agent exactly what is returned and in what order. It even names the downstream tool (breg_get_document) that the returned link feeds. It stops short of differentiating itself from sibling list tools such as breg_press_releases or breg_search, so the agent must infer the boundary.

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 'latest ... newest first' framing implies a browsing/recency use case, and the mention of breg_get_document for per-document URLs gives a clear follow-up path. However, there is no explicit statement of when to choose this over breg_search (query-driven) or breg_press_releases (a different content type), which is the main routing decision an agent faces here.

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