Skip to main content
Glama
bundesregierung-mcp

bundesregierung-mcp

breg_health

Checks whether the bundesregierung.de press-releases listing is reachable now and returns ok, blocked, or error status with the HTTP code and probed URL.

Instructions

Check whether the bundesregierung.de press-releases listing is reachable right now.

Returns status ok (HTTP 200), blocked (HTTP 403/429 — bot wall or rate limit) or error, plus the HTTP status and the probed URL. One polite request; it does not fetch any listings.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

With no annotations, the description carries the burden and does well: it enumerates the three outcome states with their HTTP meanings (200 / 403 or 429 bot wall or rate limit / error), discloses that it makes exactly one polite request, and that no listings are fetched. What is missing is any guidance on auth or rate-limit policy beyond the classification of 429.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the purpose before the return states and the non-fetching caveat. Every clause carries information an agent needs; nothing is repeated from the schema.

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 zero-parameter health probe with an output schema, the description covers purpose, return states and scope completely. The only gap is operational follow-up — it does not say whether a 'blocked' result is transient or what a caller should do next.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline applies. It correctly adds no parameter chatter, keeping the definition focused on outcomes.

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 and resource ('Check whether the bundesregierung.de press-releases listing is reachable') and pins the scope with 'right now' and 'it does not fetch any listings'. That negative clause cleanly separates it from the sibling content tools like breg_press_releases and breg_search, which do fetch listings.

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: an agent can infer it should probe reachability before relying on the listing tools, and the note that it fetches no listings signals what it is not for. However, no alternative is named explicitly and there is no when-not guidance such as what to do when the result is 'blocked'.

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