Skip to main content
Glama

billiger_health

Check whether billiger.de is reachable right now; returns ok, blocked, or error status with HTTP code and probed URL so AI agents can detect outages or bot walls.

Instructions

Check whether billiger.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": "billiger_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 supplied, the description carries the full burden and does well: it enumerates the possible outcomes (ok/HTTP 200, blocked/HTTP 403/429 from a bot wall or rate limit, error), discloses the request volume ('one polite request'), and rules out data fetching. It omits auth requirements, retry/timeout behavior, and whether blocked implies a cooldown, leaving some operational gaps.

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?

The purpose is stated in the first line, followed by return-status semantics and a scoping caveat; four short sentences with no filler. Every clause adds information an agent would otherwise have to guess.

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?

For a parameterless health probe with an output schema available, the description covers what an agent needs: what is checked, the failure taxonomy including bot-wall/rate-limit distinction, the single-request cost, and the boundary against listing tools. Nothing material is missing for correct invocation.

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 meaning to add; the baseline for a 0-param schema applies. The description correctly does not invent arguments and instead spends its words on outcomes and scope.

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 billiger.de is reachable right now') and explicitly scopes it against the price-fetching siblings by noting 'it does not fetch any listings.' An agent can distinguish this diagnostic probe from billiger_search_prices or billiger_product_offers without opening 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear context for use (a liveness probe before relying on the site) and a negative exclusion ('does not fetch any listings') that routes agents to the listing tools instead. It stops short of naming a specific sibling or stating a when-not condition explicitly, so it is strong but not exhaustive.

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