Skip to main content
Glama
Sign In
aegis-re

aegis-re

by cloudauraa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

aegis_triage_vulnerabilities

Audit source or decompiled C/C++ code for CWE security flaws such as buffer overflows, command injection, format strings, weak RNG, and hardcoded keys.

Instructions

Scans decompiled C/C++ or source code for CWE security flaws (buffer overflow, command injection, format strings, weak RNG, hardcoded keys).

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": {
      "code_or_file": "<code_or_file>"
    },
    "name": "aegis_triage_vulnerabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault
code_or_fileYesSource code text OR file path to audit

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does add real value by disclosing the detection taxonomy, so the agent knows what kinds of findings to expect. However, it says nothing about the operation's read-only nature, resource/size limits on the audited code, or what the response looks like, and the 'triage' framing in the name is never explained.

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?

A single tight sentence with the resource and the flaw taxonomy front-loaded and zero filler. It is efficient, though it spends its length on examples rather than on routing or behavioral constraints.

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

Completeness3/5

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

For a simple one-parameter tool this covers the input side adequately, but with no output schema the description should at least hint at the return shape (list of findings with CWE IDs? severity?) and whether a prior decompilation step is required. Those gaps leave an agent guessing about result handling.

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?

There is only one parameter and schema coverage is 100%, with the schema already explaining that it accepts 'Source code text OR file path'. The description adds only the qualifier that the code should be C/C++ or decompiled output, which is useful context but marginal beyond the 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?

Names a specific verb ('Scans') and resource ('decompiled C/C++ or source code') and enumerates the exact flaw classes targeted (buffer overflow, command injection, format strings, weak RNG, hardcoded keys). This clearly separates it from aegis_inspect_binary and aegis_calculate_entropy, though the siblings are never named.

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 phrase 'decompiled C/C++ or source code' implicitly scopes when the tool applies, but there is no explicit when-to-use, when-not, or routing statement relative to the sibling tools (e.g., whether aegis_inspect_binary must run first to produce decompiled code).

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