Skip to main content
Glama

Check the ZCode connection

zcode_health
Read-only

Verifies ZCode is running with its debugging port and checks that the subagent project exists, then reports how many tasks are currently running.

Instructions

Verify ZCode is running with its debugging port, the subagent project exists, and report how many tasks are running.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so ”safe read, no external side effects” is structured data. The description adds real value on top by naming the three concrete conditions that are checked, which an agent could not infer from the schema. It does not say whether a failing check produces an error or a report, so it is not fully transparent.

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 that front-loads the action and then lists the checks compactly with no filler words. Every clause contributes a distinct piece of 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 zero-parameter, read-only health check this covers the essentials: what is verified and that a task count is reported. With no output schema, a brief note on the shape of the result (pass/fail per check versus a summary) would have closed the remaining gap.

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 and the schema is trivially complete at 100% coverage, so there is nothing for the description to compensate for. Baseline 4 applies; the description correctly avoids inventing or re-stating parameter details.

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?

The description opens with a specific verb and resource ("Verify ZCode is running") and enumerates the exact checks performed: debugging port, subagent project existence, and running task count. That level of specificity separates it from siblings such as zcode_run or zcode_status, though it stops short of explicitly naming an alternative it is not.

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?

Usage is only implied: the diagnostic nature of "verify" suggests calling it as a pre-flight or troubleshooting step before running tasks. There is no explicit statement of when to call it versus zcode_status or other status tools, and no guidance on what to do with a negative result.

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