Skip to main content
Glama

dlf_health

Checks whether deutschlandfunk.de is reachable now and returns HTTP status and probed URL to distinguish OK, blocked, or error conditions.

Instructions

Check whether deutschlandfunk.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": "dlf_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 supplied, the description carries the full burden and does solid work: it discloses the three-state outcome (ok / blocked / error), maps blocked to HTTP 403 or 429 with bot-wall and rate-limit causes, and states the request cost is one polite call. It stops short of saying whether errors are network failures, timeouts or DNS problems, or whether any retry happens.

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, then the return contract, then the cost/scope constraint. Every sentence earns its place and nothing is repeated from structured fields.

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 is not obligated to document return values, yet it briefly summarizes them anyway, which is appropriate for a health probe where the semantics of 'blocked' matter. The only gap is not clarifying what conditions produce the generic 'error' state.

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 is 4. It does not invent pseudo-parameters or suggest hidden options, which keeps it clean.

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 deutschlandfunk.de is reachable right now. The scope ('right now', a single endpoint probe) clearly separates it from the sibling tools, which all retrieve content, and the closing line 'it does not fetch any listings' reinforces that distinction.

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 definition implies a clear context: a cheap pre-flight probe before invoking content tools, backed by 'One polite request; it does not fetch any listings.' However, it never explicitly says 'call this before X' or names any situation where it should be skipped, so the when-to-use guidance is strong but implicit rather than stated.

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