Skip to main content
Glama

system_doctor

Read-only

Diagnose ffmpeg, Python analysis, fonts, and folders, then run this check first when Talk-n-Edit fails to render or analyze video.

Instructions

Check ffmpeg, the Python analysis environment, fonts and folders. Run this first if anything fails.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description reinforces this by using 'Check' rather than 'fix' or 'repair', resolving the ambiguity that the 'doctor' name could otherwise create. It discloses the scope of checks but says nothing about how results are reported (per-check pass/fail vs. a single summary), which is the main remaining behavioral gap.

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 short sentences with zero filler: the first states what is checked, the second states when to run it. The ordering is effective, putting the substantive scope before the invocation cue.

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 no-parameter, read-only diagnostic with annotations covering the safety profile, the description supplies enough to call it correctly. The one gap is the absence of any statement about the shape of the result, which matters somewhat for an agent that must interpret the diagnosis, especially with no output schema.

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, so there is nothing for the description to disambiguate; the baseline of 4 applies. The description correctly implies no input is required to run the diagnostic.

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 a concrete diagnostic action and enumerates the specific subsystems it verifies (ffmpeg, Python analysis environment, fonts, folders), so an agent knows exactly what the tool covers. It doesn't explicitly contrast itself with siblings like qa_check or analysis_get, but the enumerated scope is distinctive enough to infer the boundary.

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?

'Run this first if anything fails' gives an explicit trigger condition and even a priority ordering relative to other tools. What's missing is a negative case — e.g., that it is not a repair tool or not needed on a healthy environment — so the guidance is clear but not exhaustive.

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