Skip to main content
Glama

Run All Diagnostics

fix_all
Read-onlyIdempotent

Run all diagnostics, apply safe fixes, and summarize what changed to help identify and resolve project issues.

Instructions

Run all diagnostics, apply safe fixes and summarize what changed.

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

Input Schema

NameRequiredDescriptionDefault
autoFixNoAccepted for compatibility; fixes are still advisory
projectPathNoPath to the project directory

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.7/5.0
Behavior1/5

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

The description says it will "apply safe fixes" and "summarize what changed," but the annotations declare readOnlyHint=true and destructiveHint=false, and the schema notes fixes are "still advisory." The claim of applying changes directly contradicts the read-only annotation and misleads the agent about side effects.

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 compact sentence with the diagnostic sweep front-loaded. It is efficient, but the trailing "apply safe fixes" clause is the source of the misleading behavior claim rather than earning its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an aggregating tool with no output schema, the description should clarify what the summary contains and what "safe" means. Instead it implies mutations that annotations and the schema both deny, leaving the agent with a wrong mental model of the tool's effects.

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%, and the autoFix parameter already self-documents that it is accepted only for compatibility. The description adds no further meaning about projectPath or the autoFix no-op behavior, so the schema does all the work.

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 uses a concrete verb set — run all diagnostics, apply fixes, summarize changes — so the agent knows this is a blanket diagnostic-and-fix sweep. It does not differentiate itself from siblings such as analyze_code or the narrower fix_* tools, leaving the scope of "all" ambiguous.

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 pick this over fix_javafx_headless, fix_maven_dependencies, or analyze_code, nor any prerequisite or exclusion. The agent must guess whether this is a superset of the fix_* siblings or a separate workflow.

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