Skip to main content
Glama

Health check

health_check
Read-only

Probes every data source concurrently and reports status and latency so you can verify availability and diagnose slow or failing integrations.

Instructions

Probe every data source concurrently and report status and latency.

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": "health_check"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
okYesTrue only if every registered source is healthy
sourcesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint, so the safety profile is covered. The description adds real context beyond them: it touches every source (broad, all-at-once scope) and does so concurrently, which tells an agent the call may be slow or costly against external systems. It stops short of saying how per-source failures are surfaced, which the output schema presumably handles.

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?

A single sentence with no filler, front-loading the action and following immediately with scope and output. Every clause carries information an agent needs.

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 no-parameter probe with an output schema and read-only annotations, the description supplies what it does, its coverage, and its concurrency model. The only shortfall is that it doesn't mention partial-failure behavior when one of the sources is unreachable, which matters for an open-world probe.

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 nothing for the description to disambiguate and the baseline of 4 applies. Nothing in the text conflicts with the empty schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ("probe") with an explicit scope ("every data source") and states what it returns ("status and latency"). That distinguishes it reasonably well from list_sources, which by name only enumerates sources rather than exercising them, though the description never names or contrasts that sibling explicitly.

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?

Usage is only implied: an agent can infer this is the tool for verifying connectivity/latency across sources. There is no explicit when-to-use statement, no exclusion such as "not for a single source" or alternatives like server_info, and no note about cost or how often it should be called.

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

Deploy Server

Other Tools