Skip to main content
Glama

zeit_health

Checks whether DIE ZEIT RSS feeds are reachable and reports status (ok, blocked, or error) with HTTP code and probed URL, so agents can detect bot walls or rate limits before fetching.

Instructions

Check whether the DIE ZEIT RSS feeds are 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": "zeit_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.5/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 disclosure burden and does well: it enumerates the three outcome states (ok HTTP 200, blocked HTTP 403/429 with the bot-wall/rate-limit cause, error), states the HTTP status and probed URL are returned, and notes the single polite request and that no listings are fetched. It stops short of saying whether retries or backoff occur, but the read-only, low-impact nature is unambiguous.

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?

Two short sentences plus a compact return-value line, front-loaded with the purpose before the outcome enumeration. Every clause earns its place — the status codes, the cause of the blocked state, and the no-listing caveat all prevent likely misinterpretation.

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?

The tool is simple (no inputs) and an output schema exists, yet the description still summarizes the return values in human-readable terms. Nothing an agent needs to invoke this correctly — what it probes, what it returns, what it costs — is absent.

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 no parameter semantics to add; the schema is an empty object and the description correctly does not invent inputs. Baseline of 4 applies for a no-parameter tool.

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?

The description opens with a specific verb and resource ("Check whether the DIE ZEIT RSS feeds are reachable right now"), which is immediately distinguishable from the sibling tools that actually fetch headlines/sections. An agent can tell from the first sentence that this is a connectivity probe, not a content-retrieval call.

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?

Usage is clearly implied by "reachable right now" plus the closing contrast "it does not fetch any listings," which routes the agent away from using this for content. What is missing is an explicit when-to-use statement (e.g., "call this before the listing tools when a request fails"), so the guidance is strong but inferential 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.