Skip to main content
Glama

codexswitch_health

Probes fixed local Codex switch and tunnel-client health endpoints to check whether local connectivity services are reachable and responding.

Instructions

Probe only the fixed local Codex switch and tunnel-client health endpoints.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are supplied, so the description must carry the full behavioral burden. It implies a read-only probe of fixed local endpoints, but does not say whether it makes network calls, whether it can time out or block, whether it requires a running daemon, or whether it changes any state. For a tool with zero annotation coverage this leaves meaningful ambiguity.

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 tight sentence with no filler, and the scope-limiting word 'only' is placed where it matters. Nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter read tool this is close to adequate, and the absence of an output schema means the description would ideally say what a probe result looks like (per-endpoint status, ok/failed). As written, an agent knows what it probes but not what it will receive or how to interpret a negative result.

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 no parameters and the schema is empty, so there is nothing for the description to disambiguate. Baseline of 4 applies; the phrase 'fixed local' usefully signals that no target or port can be supplied.

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 ('Probe') and resource ('Codex switch and tunnel-client health endpoints'), and the word 'only' scopes it away from any diagnostic or repair behavior. It is clear what the tool does, though the naming distinguishes it from the unrelated context_* siblings mostly by domain rather than by an explicit contrast.

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 word 'only' implies this tool is restricted to health probing and will not perform remediation or configuration, which is useful guidance. However, there is no explicit statement of when an agent should call it (e.g., before retrying a failed switch operation) or what to do with an unhealthy result.

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