Skip to main content
Glama

Code SAST Scan

code_scan
Read-onlyIdempotent

Run static application security testing (SAST) on source code to detect vulnerabilities like SQL injection, XSS, and hardcoded credentials, with CWE classifications and severity levels.

Instructions

Run SAST (Static Application Security Testing) on source code via Semgrep.

    Scans for security flaws: SQL injection, XSS, command injection,
    hardcoded credentials, insecure deserialization, path traversal, etc.
    Returns findings with CWE classifications and severity levels.

    Requires ``semgrep`` on PATH (``pip install semgrep``).
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesPath to source code directory to scan.
configNoSemgrep config. 'auto' = Semgrep Registry rules. Can be a path or registry string.auto

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint. The description adds value by stating the requirement for semgrep on PATH and that findings include CWE and severity, which are behavioral traits not covered by annotations.

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 compact: four sentences, front-loaded with purpose, then lists flaw types, output highlights, and prerequisite. No unnecessary words or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and full parameter descriptions, the description covers purpose, behavior, prerequisite, and output nature. It lacks details on typical usage context or rate limits, but these are not critical for this tool.

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?

The input schema already provides full descriptions for both parameters (path and config), so schema coverage is 100%. The description does not add further parameter semantics beyond the schema, earning a baseline score of 3.

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

Purpose5/5

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

The description clearly states the tool runs SAST via Semgrep, lists specific flaw types (SQL injection, XSS, etc.), and mentions output includes CWE and severity, distinguishing it from sibling tools like generic 'scan' or 'compliance'.

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 provides clear context: use for security scanning of source code. It includes a prerequisite (semgrep on PATH). However, it does not explicitly exclude when not to use it or mention specific alternatives among siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/msaad00/agent-bom'

If you have feedback or need assistance with the MCP directory API, please join our Discord server