Skip to main content
Glama
spiegel-mcp

spiegel-mcp

spiegel_health

Check whether spiegel.de is reachable now, returning ok, blocked, or error with the HTTP status and probed URL so you can verify availability before fetching content.

Instructions

Check whether spiegel.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": "spiegel_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.3/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 reasonably well: it discloses the outcome taxonomy (ok/blocked/error), maps blocked to 403/429 and explains those as bot wall or rate limiting, and notes the request is a single polite call that fetches no listings. It stops short of stating anything about auth, caching, timing, or retry behavior, so it is strong but not exhaustive.

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 core purpose, then the result taxonomy, then the cost/scope caveat. No filler, no repetition of the name or title.

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?

This is a zero-parameter health probe with an output schema, so the description only needs to convey purpose, outcome meanings, and cost. It covers all three; an agent has everything required to call it and interpret the result correctly.

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, which is the baseline-4 case; there is nothing for the description to disambiguate. The mention of 'the probed URL' clarifies implicitly that the target is fixed and not caller-supplied, which is a small useful addition.

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 — checking whether spiegel.de is reachable right now — and the final sentence ('it does not fetch any listings') functionally separates it from the content-oriented siblings like spiegel_headlines and spiegel_get_article. An agent can pick this tool without inspecting any schema.

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 'reachable right now' phrasing implies a pre-flight/liveness use case, and 'does not fetch any listings' excludes content retrieval, but there is no explicit when-to-use or when-not-to-use statement and no mention of what to do depending on the result. Guidance is implied rather than stated.

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