Skip to main content
Glama

defense-gateway

audit_sunat_cpe_xml

Auditoría forense determinista de facturas y comprobantes electrónicos XML UBL 2.1 SUNAT Perú (Módulo 11 de RUC, cuadre del 18% IGV y validación de firma).

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": {
      "xml_content": "<xml_content>"
    },
    "name": "audit_sunat_cpe_xml"
  }
}

Input Schema

NameRequiredDescriptionDefault
xml_contentYesContenido XML del comprobante UBL 2.1
strict_tax_checkNoExigir cuadre aritmético estricto de IGV al centavo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses the audit dimensions and that the audit is 'determinista' (reproducible, no heuristics), but it never states that the tool is a pure read/compute operation with no side effects, what a failed signature or unbalanced IGV produces, or how results are reported.

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-phrase with the domain and the three audit dimensions front-loaded inside parentheses; there is no filler. It is, however, a noun phrase rather than a statement of action, and the parenthetical check list compresses several ideas into one unpunctuated clause.

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 2-parameter, 100%-documented-schema tool this is close to adequate, but with no output schema and no annotations the description should say something about the shape of the audit verdict (pass/fail, findings list) and whether the signature check needs certificates or trust material. It also is written only in Spanish, which may reduce clarity for a non-Spanish-speaking planner.

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. The description adds partial context by naming 'cuadre del 18% IGV' and 'validación de firma', which hint at what strict_tax_check governs, but it adds no syntax or format detail 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?

The description names a specific resource and operation: forensic deterministic audit of SUNAT Peru electronic invoices in UBL 2.1 XML, and enumerates the concrete checks (RUC modulo-11, 18% IGV reconciliation, signature validation). That is far more specific than a sibling like audit_excel_macro_forensics or match_peruvian_procurement, though it never names a sibling to contrast against explicitly.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance: nothing says whether this should be run before/after match_peruvian_procurement, whether it applies only to Peruvian SUNAT documents, or what to do when the XML is from another jurisdiction. Use must be inferred entirely from the domain phrase 'auditoría forense'.

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.