Skip to main content
Glama

A2A Defense & Monetization Gateway

audit_excel_macro_forensics

Auditoría forense estática de código VBA de macros Excel y desofuscación de identificadores de confusión visual (WinAPI, Shell, credenciales y URLs).

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": {
      "vba_code": "<vba_code>"
    },
    "name": "audit_excel_macro_forensics"
  }
}

Input Schema

NameRequiredDescriptionDefault
vba_codeYesCódigo fuente VBA para auditar e inspeccionar
auto_deobfuscateNoNormalizar identificadores ofuscados confusos (O/0/l/1)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 valuable work by declaring the analysis is static (implying the macro is not executed) and naming the suspicious categories inspected, but it says nothing about permissions, size limits, or what the audit produces, which matters for a no-annotation tool.

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 dense sentence with the primary function front-loaded and the secondary capability appended. It is efficient, though the trailing parenthetical is compressed enough to be unclear rather than informative.

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 two-parameter tool with full schema coverage this is close to adequate, but with no annotations and no output schema the description never hints at the shape of the result (findings list, risk verdict, matched indicators). An agent knows what to send but not what it will get back.

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?

Schema description coverage is 100%, so both parameters are already documented, establishing a baseline of 3. The description's mention of 'desofuscación de identificadores de confusión visual' loosely reinforces the auto_deobfuscate flag but adds no syntax or default behavior beyond what the schema already states.

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?

States a specific verb and resource: static forensic audit of VBA macro code, plus a secondary function (deobfuscation of visually confusable identifiers). The parenthetical '(WinAPI, Shell, credenciales y URLs)' is ambiguous — it is unclear whether these are detection targets or examples of confusable identifiers — which keeps it short of a 5.

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 'auditoría forense estática' implies the context (analyzing untrusted/suspicious macros without execution), but there is no explicit when-to-use, when-not-to-use, or prerequisite statement. No sibling is named or ruled out, though the sibling list contains no near-equivalent, so the gap is low-impact.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources