Skip to main content
Glama
Sign In
Spotter-SAST

Spotter-SAST

by george-mellow
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

scan_directory

Scans a directory to identify security vulnerabilities through static application security testing.

Instructions

Legacy: Use enhanced_scan_directory 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": {
      "dirpath": "<dirpath>"
    },
    "name": "scan_directory"
  }
}

Input Schema

NameRequiredDescriptionDefault
dirpathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

D1.8/5.0
Behavior1/5

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

No annotations are provided, and the description does not disclose any behavioral traits such as side effects, authorization needs, or return behavior. The only information is that it is legacy.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is one short sentence, which is concise, but it lacks structure and does not serve as a proper tool description. It reads as a warning rather than informative content.

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?

Given the tool's simplicity (one parameter, no output schema), the description is insufficient. It does not explain the tool's original purpose or why it is legacy, leaving the agent with no understanding of the tool's functionality.

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 input schema has one required parameter (dirpath) with no description, and schema description coverage is 0%. The description adds no meaning to the parameter, failing to compensate for the lack of schema documentation.

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

Purpose1/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. It only says 'Legacy: Use enhanced_scan_directory instead,' which is a deprecation notice, not a description of the tool's function.

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

Usage Guidelines4/5

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

The description clearly advises against using this tool and explicitly names the alternative (enhanced_scan_directory). This provides strong usage guidance, although it doesn't explain when one might still need to use this legacy version.

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

Deploy Server

Other Tools