Skip to main content
Glama

zdf_health

Check whether zdfheute.de is reachable right now, returning status ok, blocked, or error with the HTTP status and probed URL to diagnose bot walls or rate limits.

Instructions

Check whether zdfheute.de 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": "zdf_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.4/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 well: it enumerates the three possible outcomes (ok=200, blocked=403/429 bot wall or rate limit, error), notes the returned HTTP status and probed URL, and discloses the request cost ("one polite request") plus a side-effect boundary (does not fetch listings). It stops short of saying whether results are cached or how quickly blocking states resolve.

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?

Four short sentences with the action front-loaded, followed by return values and then the cost/side-effect caveat. Nothing repeats the name and nothing is padding.

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?

An output schema exists, so the description did not need to enumerate return values, yet it still names the three status categories usefully. For a zero-parameter probe with no annotations, the only remaining gap is the absence of any explicit read-only/no-mutation statement, which is strongly implied by "one polite request" but never declared.

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 clarify beyond what the empty schema already shows. Baseline 4 applies.

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 zdfheute.de is reachable") with immediate timing scope ("right now"). It is clearly distinguishable from the siblings, which fetch articles, headlines, topics, or search results rather than probing availability.

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?

The closing line "One polite request; it does not fetch any listings" tells the agent this is a lightweight pre-flight/diagnostic call rather than a data source, effectively steering it away from using this for content. It never explicitly says "call this before zdf_get_article when you suspect blocking," so the when-to-use linkage to siblings is implied rather than spelled out.

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