Skip to main content
Glama
SurveyBridge AI

SurveyBridge AI

by onovo007

surveybridge_healthcheck

Returns local server version and configuration details for diagnostics, without verifying remote availability.

Instructions

Return local server version and configuration; does not assert remote availability.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
dataNo
sourceNo
statusNook
warningsNo
truncatedNo
paginationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden: it implies a side-effect-free read and explicitly limits the claim to local state, which is genuinely useful negative information. It omits whether auth is required, whether configuration is returned in full (possibly containing secrets), and any cost/latency expectations.

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 the primary action front-loaded and the important caveat attached after the semicolon. No filler, no repetition of the tool name.

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?

Zero parameters and an output schema already covering the return shape mean little more is needed; the local-versus-remote caveat fills the main ambiguity. Minor residual gap is whether the response reflects credentials/authorization state or just build metadata.

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 of 4 applies; there is nothing for the description to disambiguate. The description's only semantic addition, 'local', correctly tells the agent no target/host argument is expected.

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?

States a specific verb ('Return') and a specific resource ('local server version and configuration'), which is clearly distinct from the data-query siblings in the surveybridge family. It doesn't name or route against any sibling, but the diagnostic nature makes it self-evidently separable.

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?

The clause 'does not assert remote availability' implicitly scopes the tool to local checks and warns against using it as a remote liveness probe. However, there is no explicit statement of when to call it or which alternative to use for remote checks, so usage is only implied.

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