Home / Reports / mcp-builder

mcp-builder

Validated 5 Jun 2026 · Repository

PRO

Needs Work

0 critical

3 warnings

24 suggestions

82 passed

Domain scores

Anti-Slop

100

Accessibility

100

Enterprise

100

Issues

Warnings (3)

16.1-no-stop-conditionline 7

Complex skill lacks explicit stop conditions

Fix: Add stop/termination criteria (e.g., 'Stop after N iterations', 'Abort if error rate exceeds threshold')

19.2-reviewer-no-criterialine 7

Reviewer pattern detected but no evaluation criteria documented

Fix: Add a criteria section (checklist, rubric, or pass/fail conditions)

19.3-generator-no-output-specline 7

Generator pattern detected but no output format specified

Fix: Document the output format (template, schema, or example output)

Suggestions (24)

2.9-mcp-tool-unqualifiedline 68

MCP tool reference 'mcp_best_practices' may need server prefix

Fix: Use fully qualified MCP tool names: ServerName:tool_name (per best practices)

2.9-mcp-tool-unqualifiedline 72

MCP tool reference 'python_mcp_server' may need server prefix

Fix: Use fully qualified MCP tool names: ServerName:tool_name (per best practices)

2.9-mcp-tool-unqualifiedline 76

MCP tool reference 'node_mcp_server' may need server prefix

Fix: Use fully qualified MCP tool names: ServerName:tool_name (per best practices)

17.1-no-input-contractline 7

No input contract found; unclear what data the skill expects

Fix: Document what the skill expects as input (format, required fields, constraints)

17.2-no-output-contractline 7

No output contract found; unclear what the skill produces

Fix: Document what the skill produces (format, structure, side effects)

14.2-no-examplesline 1

No input/output examples found

Fix: Add example input/output pairs or <example> blocks to make the skill testable

3.4-gerund-namingline 2

Skill name could use gerund form for clarity

Fix: Consider gerund-style names like 'processing-pdfs' or 'analyzing-logs' (per best practices)

18.1-no-confidence-signalline 1

No confidence signal found for orchestrator decision-making

Fix: Add confidence indicators (e.g., confidence: high/medium/low) so orchestrators can route or retry

18.2-no-progress-signalline 1

Complex skill lacks progress reporting checkpoints

Fix: Add progress signals (e.g., 'Step 2 of 5: validating input') for long-running workflows

18.3-no-structured-outputline 1

No structured output format defined for machine consumption

Fix: Define a structured output format (JSON, YAML, or table) so downstream tools can parse results

19.6-wrapper-no-boundaryline 7

Tool Wrapper pattern detected but no API boundary documented

Fix: Document what the wrapped tool can and cannot do (scope, limitations)

4.2-ambiguous-termline 44

Ambiguous term 'proper' found