PC-Fixer MCP Server

pc_fixer_diagnose

Runs deep multi-tier diagnostics across workspace code, OS environment, virtual environments, Git locks, build configs, AST syntax, and CWE vulnerabilities to identify issues before repair.

Instructions

Run deep multi-tier diagnostics across workspace code, operating system environment, virtual environments, Git repository locks, PEP 517 build configs, AST syntax, and CWE vulnerabilities.

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

Input Schema

Name	Required	Description	Default
`path`	No	Workspace root directory to diagnose (default: current directory)	.
`categories`	No	Optional list of categories to filter (e.g. ['syntax', 'environment', 'security', 'workspace'])

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 5, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. "Diagnostics" implies a read-only scan, but the description does not explicitly state that it is non-mutating, what permissions or runtime it needs, whether it is slow or resource-intensive, or what kind of report it returns; with no output schema either, this leaves material gaps.

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?

The description is a single front-loaded sentence with no wasted wording. It compresses a broad set of diagnostic domains into one efficient list, and every phrase contributes to scoping the tool.

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 a complex multi-domain diagnostic tool with no annotations and no output schema, one sentence is not enough. It should explain the read-only nature, expected output, and when this broad diagnostic is preferable to narrower sibling tools, none of which are covered.

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 the path and categories parameters are already documented in the schema. The description lists diagnostic domains that loosely correspond to category filters, but it adds no explicit semantics for the path default or category filtering beyond what the schema provides, making the baseline 3 appropriate.

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 verb and resource: "Run deep multi-tier diagnostics" across named areas including workspace code, OS environment, Git locks, PEP 517 configs, AST syntax, and CWE vulnerabilities. It is clear what the tool does, but it does not explicitly distinguish itself from overlapping siblings such as pc_fixer_check_system or pc_fixer_cwe_audit.

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 guidance on when to use this tool versus alternatives. With siblings like pc_fixer_check_system, pc_fixer_cwe_audit, and pc_fixer_auto_heal, the description should say whether this is the broad umbrella diagnostic or when a narrower sibling is preferable, but it provides no such routing.

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

Deploy Server