Skip to main content
Glama

Verify credentials and upstream reachability

iaqualink_healthcheck
Read-onlyIdempotent

Diagnoses a failed pool tool call by checking credential resolution and one authenticated request to r-api.iaqualink.net, reporting source, acceptance, latency, and which hop broke.

Instructions

Resolves the credential the way real tools do, then makes one authenticated request to r-api.iaqualink.net. Reports which source supplied the credential, whether r-api.iaqualink.net accepted it, the round-trip time, and a plain-English hint distinguishing 'no credential' from 'credential rejected' from 'a r-api.iaqualink.net-side problem'. Read-only; never returns the credential itself. Call this when a real tool fails and you want to know which hop broke.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, but the description adds meaningful extras: that it performs a real authenticated network call to a named host, that it never returns the credential itself, and that failure output is a plain-English hint categorizing the problem into three distinct buckets. The only minor gap is that it doesn't say what a rate limit or non-JSON response from the upstream produces.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core behavior and the trigger come first, followed by what it reports — good front-loading with no filler. The host name r-api.iaqualink.net is spelled out three times in four sentences, which is mild redundancy.

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?

There is no output schema, so the description carries the return-value burden and does so: it enumerates the four things reported (source, acceptance, latency, hint) and the three failure categories the hint distinguishes. For a zero-parameter diagnostic, nothing needed for correct invocation 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 there is nothing for the description to disambiguate; the baseline for a parameterless schema applies. No parameter meaning is lost or misstated.

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 names a specific action (resolve credential, make one authenticated request to r-api.iaqualink.net) and a specific deliverable (credential source, acceptance status, round-trip time, diagnostic hint). No sibling tool does diagnostics, so the agent can distinguish this from the mutating iaqualink_set_* and read-only iaqualink_get_status/list_* tools on the description alone.

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 an explicit trigger: "Call this when a real tool fails and you want to know which hop broke," which clearly separates it from the operational siblings. It does not state when this would be unnecessary (e.g., when the failure is obviously a bad parameter rather than a connectivity problem), so it stops just short of full when/when-not coverage.

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