Skip to main content
Glama

jdx_health

Verify server liveness and return uptime, the served workspace, and the answered query count.

Instructions

Liveness probe: uptime, workspace served and queries answered.

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

Input Schema

NameRequiredDescriptionDefault
queryNoOptional label echoed back in the envelope (empty is fine).
workspaceNoNamed workspace to answer from (default: the workspace the server was started with). Stored workspaces only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.7.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. 'Liveness probe' implies a safe, side-effect-free read, and the phrase lists the fields returned (uptime, workspace served, queries answered), but it never explicitly states that the call is read-only, whether it touches storage, or how expensive it is.

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?

A single front-loaded fragment with no filler; the key term 'liveness probe' leads. It is slightly telegraphic — 'queries answered' is undefined and the sentence is a noun phrase rather than a statement of action.

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 two-optional-parameter read-only probe with no output schema, the description is roughly adequate: it sketches the returned fields. It is missing any note that the call is harmless/idempotent and what 'queries answered' counts, which an agent evaluating diagnostics would want.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so both optional parameters (query label echo and workspace selection, including the 'stored workspaces only' constraint) are already documented in the schema. The description adds nothing about parameters, which is acceptable at this coverage level but warrants no credit.

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 names the tool's role (liveness probe) and enumerates what it reports: uptime, workspace served, and queries answered. That is specific enough to know what calling it yields, but it does not distinguish it from neighboring diagnostic tools such as jdx_version or jdx_doctor.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to call this probe versus jdx_version or jdx_doctor, nor any exclusions or prerequisites. An agent must infer that this is a cheap health check from the words 'liveness probe' alone.

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