Skip to main content
Glama
ntv-mcp

ntv-mcp

ntv_health

Checks whether n-tv.de is reachable and reports HTTP status plus ok, blocked, or error state, helping diagnose access or rate-limit issues with one polite request.

Instructions

Check whether n-tv.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": "ntv_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?

No annotations are supplied, so the description bears the full burden, and it does disclose meaningful behavior: the three possible verdicts and what each means (ok=200, blocked=403/429 bot wall or rate limit, error), the returned HTTP status and probed URL, and that it issues exactly one polite request that does not fetch listings. It omits timeout/duration and any auth or rate-limit constraints on calling the tool repeatedly.

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 question, then the return vocabulary, then the cost/scope caveat. No repetition of the tool name and no filler.

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 present, this is nearly complete: it explains the status vocabulary and states the request cost. The only omission an agent might want is expected latency or timeout behavior, which is minor given the output schema covers the return shape.

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 the baseline is 4 and there is no parameter meaning for the description to add. Nothing here conflicts with the empty schema.

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 n-tv.de is reachable right now.' It also names its own scope explicitly, and the closing note that it 'does not fetch any listings' implicitly separates it from content-fetching siblings like ntv_headlines and ntv_get_article.

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 framing 'reachable right now' plus 'does not fetch any listings' makes it clear this is a liveness probe rather than a content call, which is real context an agent can act on. It stops short of explicit routing such as 'use this before retrying a failed fetch' or when not to call it, so it falls short of full when/when-not guidance.

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