Skip to main content
Glama

UAI x402 Security Tools

compliance-evidence-mapper

Map SOC 2, ISO 27001, HIPAA, PCI, and GDPR compliance audit requests to evidence items, owners, systems, and follow-up questions. For agent-driven compliance and audit workflows. (REST equivalent: POST /api/v1/compliance-evidence-mapper, $0.15)

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": {
      "subject": "<subject>",
      "body": "<body>",
      "framework": "<framework>"
    },
    "name": "compliance-evidence-mapper"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesEvidence request body
subjectYesEvidence request subject
frameworkYesCompliance framework (soc2, iso27001, etc.)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations carry only a title, so the description bears the disclosure burden; it does add real value by naming the output components (evidence items, owners, systems, follow-up questions) and the per-call price of $0.15 via the REST endpoint. It does not say whether results are persisted, whether any account/permission is required, or how many requests it accepts per call. Adequate but with clear behavioral gaps for a tool with no safety hints at all.

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?

Two sentences plus a short parenthetical, with the primary capability front-loaded and pricing/endpoint demoted to the end. Essentially no filler; the only mild noise is the pricing parenthetical, which is still actionable information for an agent.

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?

No output schema exists, and the description steps in by enumerating what the response contains, which is the single most important missing piece. Combined with full schema coverage on the three string parameters and a stated price, an agent has enough to call this correctly; only limits, error behavior, and side-effect disclosure are absent.

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 coverage is 100%, so baseline is 3. The framework list (SOC 2, ISO 27001, HIPAA, PCI, GDPR) loosely enriches the 'framework' parameter by implying accepted values, but it does not state the expected token format ('soc2', 'iso27001') that the schema hints at, and it adds nothing about how 'subject' and 'body' should be composed.

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?

Uses a specific verb ('Map') plus concrete inputs and outputs: compliance audit requests across five named frameworks, resolved to evidence items, owners, systems, and follow-up questions. That is far more informative than the bare name. It lacks an explicit contrast with related siblings like gdpr-privacy-scan or policy-genie, so it is clear but not fully disambiguated.

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 line 'For agent-driven compliance and audit workflows' gives a general context for use, which is more than nothing. There is no guidance on when not to use it, no prerequisites, and no mention of neighboring tools the agent should pick instead for adjacent tasks.

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