Skip to main content
Glama

Live source health check

check_source_health
Read-only

Pings every upstream Swiss data source behind active modules to report status and latency; use when another tool flags a source as unavailable.

Instructions

Ping every upstream Swiss data source behind the active modules and report status and latency, Swissyphus's built-in status page. Use when another tool reports a source as unavailable.

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

Input Schema

NameRequiredDescriptionDefault
moduleNoOptionally check only one module, e.g. 'transport'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the agent knows this is a safe external read. The description adds that it pings every upstream source and reports latency, but it does not disclose timeouts, cost, expected duration, or what status values mean.

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 definition is two compact sentences with the purpose and triggering condition front-loaded. There is no redundant or filler text.

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 one-parameter health-check tool with no output schema, the description provides enough context to select and invoke it. It states what is checked and what is reported, though it could say more about the response or expected latency.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, and the single optional 'module' parameter is fully documented in the schema with an example. The description does not mention the parameter, so it adds little beyond the structured schema, which is acceptable at this coverage level.

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 description uses a specific verb and resource: it pings upstream Swiss data sources behind active modules and reports status and latency. It also distinguishes itself as the built-in status page, making the tool's role clear compared with data-query siblings.

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?

It gives a clear triggering condition: 'Use when another tool reports a source as unavailable.' That is useful guidance, though it does not state when not to use the tool or name alternative diagnostic paths.

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