Spotter-SAST

Overview Schema Source Related Servers Discussions Admin

scan_file

Scans a specified file for static security vulnerabilities using legacy method. For improved analysis, use the enhanced scan tool.

Instructions

Legacy: Use enhanced_scan_file instead

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

Input Schema

Name	Required	Description	Default
`filepath`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.0May 26, 2026

TDQS

C2.8/5.0

Behavior2/5

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

The only behavioral trait disclosed is that the tool is legacy/deprecated. No other behavior (e.g., what it does, side effects, permissions) is described, and no annotations exist to fill the 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?

A single, brief sentence that conveys the essential deprecation message without any filler.

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 legacy tool, the description is too sparse. It does not explain the tool's function, return values, or whether it still works, which may confuse an agent considering invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has one parameter (filepath) with 0% description coverage, and the description adds no information about it, failing to compensate for the schema gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description does not state what the tool does (e.g., scans a file for vulnerabilities). It only marks it as legacy and directs to enhanced_scan_file, which implies a scanning function but leaves the purpose vague.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says to use enhanced_scan_file instead, providing clear guidance on when not to use this tool and a direct alternative.

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