Skip to main content
Glama

fs_health

Checks whether fernsehserien.de is reachable right now and reports status ok, blocked, or error with HTTP status and probed URL.

Instructions

Check whether fernsehserien.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": "fs_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.2/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations present, the description carries the burden and does well: it enumerates the three possible outcomes (ok/blocked/error) with their HTTP codes, explains that blocked means a bot wall or rate limit, and discloses the side-effect profile ('one polite request', no listing fetch). It stops short of mentioning timeouts, retry advice, or whether the probe is cached.

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 and status semantics, with the scope disclaimer last. Every sentence adds information; nothing is redundant.

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?

A no-parameter diagnostic tool with an output schema is well served by this description, which covers the outcome vocabulary an agent needs to branch on ('blocked' vs 'ok'). Minor gaps remain around timeouts and what an agent should do on each outcome, but nothing essential is missing.

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; the description usefully confirms the URL is fixed per call rather than caller-supplied ('the probed URL').

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 fernsehserien.de is reachable right now') and the clarifying clause 'it does not fetch any listings' separates it from the sibling data-fetching tools (fs_search_series, fs_episodes, etc.) without needing their schemas.

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 phrase 'right now' and the note that it fetches no listings imply it is a pre-flight/diagnostic probe before real requests, but it never explicitly says 'call this before X' or 'use this when another tool returns errors'. Usage is inferable rather than stated, and no alternative is named.

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