Skip to main content
Glama
Sign In
ThriftyRelay

ThriftyRelay

by Roseu7
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Remote Health

health
Read-only

Checks whether the local MCP endpoint is reachable and returns a brief connection status.

Instructions

Confirm this local MCP is reachable. Returns only brief connection status.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds genuinely useful context that no output schema provides: the return is only a brief connection status. It does not say what happens on failure (error vs. negative status), which is the one behavior an agent most needs to plan around.

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?

Two short sentences, zero waste, with the action front-loaded and the return contract immediately after. Nothing could be removed without losing information.

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 parameterless, annotated, read-only tool with no output schema, this covers what the agent needs: what it does and what it returns. The only gap is failure-mode behavior and the local-vs-remote naming mismatch, which are minor.

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?

Zero parameters, so the baseline of 4 applies; there is nothing for the description to clarify. The schema explicitly forbids additional properties, consistent with the description implying a bare call.

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?

A specific verb ("Confirm") plus a concrete resource (reachability of this local MCP) makes the function unmistakable, and no sibling (approvals, tasks, settings, inspect) overlaps with a connectivity check. It stops short of naming or excluding any sibling, so it does not actively differentiate.

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?

Use is implied — an agent would ping this to verify the server is alive before/after other operations — but the description states no explicit when-to-use, when-not-to-use, or alternative. The persistent ambiguity between the title "Remote Health" and "this local MCP" also leaves the target of the check slightly unclear.

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