Spotter-SAST

by george-mellow

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

ai_enhanced_auto_fix

Apply AI-powered fixes to code security vulnerabilities. Validates each change and enables rollback via backup.

Instructions

Apply AI-powered intelligent fixes with validation and rollback capability

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "filepath": "<filepath>"
    },
    "name": "ai_enhanced_auto_fix"
  }
}

Input Schema

Name	Required	Description	Default
`filepath`	Yes	Absolute path to the file to fix
`finding_ids`	No	Specific finding IDs to fix
`strategy`	No	Fix application strategy	balanced
`validate_fixes`	No	Validate fixes before applying
`create_backup`	No	Create backup before applying fixes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.0May 26, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Mentions validation and rollback capabilities but lacks specifics on behavioral implications (e.g., file modification, permissions, side effects). No annotations provided.

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?

Single sentence, no wasted words, effectively conveys core purpose.

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?

With 5 parameters and no output schema, description lacks detail on validation, rollback semantics, and strategy differentiation.

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 covers 100% of parameters with descriptions; description adds minimal extra meaning beyond schema.

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?

Clearly states 'Apply AI-powered intelligent fixes' with validation and rollback, but does not explicitly distinguish from sibling 'auto_fix_file'.

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?

No guidance on when to use this tool vs alternatives like auto_fix_file, or when not to use it.

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