Skip to main content
Glama

tabii_health

Checks whether tabii.com is reachable now and reports HTTP status plus probed URL, distinguishing OK, blocked, and error responses.

Instructions

Check whether tabii.com 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. Two polite requests (homepage + one public show); 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": "tabii_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.7/5.0
Behavior5/5

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

There are no annotations, so the description carries the full burden, and it does so well: it discloses the exact request footprint ('two polite requests (homepage + one public show)'), the possible outcome taxonomy (ok/blocked/error) with the HTTP codes that map to each, and the fact that no listings are fetched. That is precisely the side-effect and failure-mode information a caller needs before invoking a network probe.

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 front-loaded in the first sentence, followed by outcome semantics and then request behavior, with no filler. The parenthetical gloss on 403/429 as 'bot wall or rate limit' is directly actionable and earns its space.

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?

An output schema exists, so the description need not enumerate return fields, and it still summarizes the status taxonomy. For a zero-argument health probe, nothing an agent needs in order to call it or interpret a failure 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, so the baseline is 4; there is nothing parameter-related the description could usefully add. The mention of the probed URL clarifies what is implicitly probed in the absence of input.

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?

The first sentence states a specific verb and resource: checking whether tabii.com is reachable right now. It also distinguishes the tool from the content-retrieval siblings by explicitly noting it 'does not fetch any listings,' so there is no ambiguity with tabii_homepage or tabii_get_show.

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 negative scoping clause ('does not fetch any listings') implicitly routes the agent to the sibling content tools when it wants actual data. It does not explicitly say when to prefer this probe (e.g., before a batch of calls, or to diagnose failures), so the guidance is clear but not complete.

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