Skip to main content
Glama
Sign In
secureaudit-mcp

secureaudit-mcp

by rev2ret
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

audit_source_code

Detects critical secure coding issues in C/C++ source code, including stack buffer overflows, unsafe function usage, format string exploits, and memory leaks.

Instructions

Scans C/C++ source code files for critical secure coding issues such as stack buffer overflows, gets/strcpy usage, format string exploits, command injections, and memory leaks.

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

Input Schema

NameRequiredDescriptionDefault
filePathYesAbsolute path to the C/C++ source code file to audit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the full burden. It states the tool scans for issues, implying a read-only analysis, but does not disclose if it modifies files, requires network access, or has other side effects.

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 a single sentence that efficiently conveys the tool's purpose and scope without unnecessary words.

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?

The description lacks information about output (e.g., does it return a list of issues, a report?) and does not mention any prerequisites or side effects. Since there is no output schema, the description should clarify what the tool delivers.

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 has 100% coverage with a clear description for the only parameter 'filePath'. The tool description adds context about the scan's focus but does not enhance parameter semantics beyond the schema.

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 it scans C/C++ source files for specific secure coding issues like buffer overflows and memory leaks. The tool name 'audit_source_code' and examples differentiate it from siblings that handle binaries, remediation, or string extraction.

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

Usage Guidelines3/5

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

The description implies use on C/C++ source files but provides no explicit guidance on when to use vs. alternatives or when not to use. Siblings suggest different scopes, but the description could be clearer.

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