Skip to main content
Glama

A2A Defense & Monetization Gateway

request_epistemic_audit

Ejecuta una auditoría de verdad factual pagada mediante token de micropago.

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": {
      "service_request_json": "<service_request_json>"
    },
    "name": "request_epistemic_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
service_request_jsonYesJSON serializado del ServiceRequest (incluyendo el PaymentToken).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/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 only hints that the audit is 'pagada mediante token de micropago,' without disclosing whether tokens are consumed on failure, whether calls are idempotent, what permissions are needed, or how long an audit takes — all critical for a paid operation.

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 front-loaded sentence with no filler; the verb and the payment condition come immediately. It is efficient, though its brevity borders on under-specification rather than optimal concision.

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?

For a paid, mutation-adjacent operation with no annotations and no output schema, the description says nothing about return values, cost implications, error behavior, or how the micropayment interacts with the audit result. An agent could call it but could not predict the outcome or risk.

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% and the single parameter already documents that it is a serialized ServiceRequest including the PaymentToken. The description adds no further meaning about the JSON structure, token placement, or validation rules, so it sits at the baseline.

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 states a concrete verb and resource ('Ejecuta una auditoría de verdad factual') plus the payment mechanism, so an agent knows this is a fact-checking audit rather than an Excel/SUNAT audit like its siblings. It stops short of explicitly differentiating itself from the other audit_* tools, so it lands at 4 rather than 5.

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, no mention of prerequisites beyond the payment token, and no pointer to alternatives such as request_l402_challenge or verify_l402_payment for the payment flow. The agent must infer all selection criteria.

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