Skip to main content
Glama

jdx_doctor

Explains why environment diagnostics are refused over MCP and directs you to run jdx doctor in a shell to inspect the server's machine instead.

Instructions

Environment report. The server refuses this over MCP — it describes the server's machine, not the client's — run jdx doctor in a shell instead.

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

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

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the behavioral burden and does disclose the critical trait: the call will be refused rather than return a report, plus the reason. It doesn't spell out what the refusal envelope looks like or whether the query label is still echoed, which keeps it off a 5.

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 compact sentences, front-loaded with the outcome and immediately followed by the redirect. No filler and nothing the agent must read past to learn the tool is unusable over MCP.

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 two-optional-parameter, annotation-free tool with no output schema, this is nearly complete: it tells the agent the call fails and what to do instead. The remaining gap is the exact refusal behavior and whether any payload is returned.

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 parameters are already documented in structured form and the baseline applies. The description adds no meaning about query or workspace, and given the tool refuses over MCP their effect is left implicit.

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 states the resource ('Environment report') and, more importantly, what actually happens when the tool is invoked: the server refuses the call over MCP. That verb+outcome framing lets an agent distinguish it from siblings without opening the schema. It falls short of a 5 only because 'environment report' is not sharply differentiated from neighbors like jdx_health or jdx_version.

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

Usage Guidelines4/5

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

It gives explicit when-not-to-use guidance: don't call this over MCP, run `jdx doctor` in a shell instead. That is a concrete alternative action with a stated condition (the report describes the server's machine, not the client's). No sibling tool is named, but the redirect is unambiguous.

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