Skip to main content
Glama

Check the setup

doctor
Read-only

A checklist to run on this computer for Cuttr skills (ffmpeg, Python, Node, Whisper, connectors), with the fix for each missing piece. Pass a slug to check only what that skill needs.

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

Input Schema

NameRequiredDescriptionDefault
slugNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true, and the description is consistent with a non-mutating diagnostic. It adds real behavioral context beyond the annotations: the check inspects five named dependency categories and the response includes the fix for each missing piece, which tells the agent the output is actionable remediation, not just a pass/fail. It stops short of clarifying whether it verifies versions or how failures are surfaced.

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 tight sentences with no filler. The scope and content of the checklist come first, and the optional parameter behavior is appended second, which is the right priority order.

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 one-optional-parameter read-only diagnostic with no output schema, the description covers the essentials: what is inspected, what the output contains (fixes), and how to narrow scope. Minor gaps remain around output shape and whether versions are reported, but nothing prevents correct invocation.

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?

Schema description coverage is 0%, so the description carries the burden for the single 'slug' parameter. It does: the slug scopes the check to one skill's requirements, and the phrasing implies omitting it runs the full checklist. That is meaningful guidance absent from the raw schema, though it doesn't say whether slug must match a value from list_skills.

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 a specific diagnostic action over a specific resource: an environment checklist covering ffmpeg, Python, Node, Whisper and connectors. An agent can tell this is an environment/skill-dependency check rather than a setup-mutation or a report. It does not name the closest sibling (setup_step), so differentiation is left implicit.

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?

"A checklist to run on this computer" establishes the context, and "Pass a slug to check only what that skill needs" gives a clear narrowing condition. However, there is no guidance on when to prefer this over setup_step or report_problem, and no statement of what to do after the checklist reports a failure.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources