Skip to main content
Glama

KEVAREMESH Free Agent API Gateway

Re-deliver your already-paid API result using a verified receipt

kevaremesh_retrieve_paid_api_result

One existing receipt completes automatic on-chain reconciliation when possible, then retrieves the original AES-GCM cached paid result in the same MCP tool call. If confirmation is pending, retry this receipt tool later without re-paying. Result cache lasts up to 24 hours. No new signature, payment, provider call or algorithm execution.

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": {
      "receipt_id": "<receipt_id>"
    },
    "name": "kevaremesh_retrieve_paid_api_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
receipt_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does well: it discloses that no new signature, payment, provider call or algorithm execution occurs, that reconciliation is attempted automatically, that the cache holds results for up to 24 hours, and that pending confirmation should be retried rather than repaid. It omits failure states – what happens with an invalid, expired, or never-paid receipt – and any auth requirements.

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?

Three front-loaded sentences, each carrying distinct value: the mechanism, the pending-confirmation retry rule, the 24-hour cache lifetime, and the no-new-payment guarantee. Dense and jargon-heavy ('AES-GCM', 'on-chain reconciliation') but no sentence is filler.

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?

For a single-parameter tool with no annotations and no output schema, the description covers what is returned (the original cached paid result), the lifetime constraint, and the retry path. The remaining shortfall is error/edge-case behavior, which matters for an agent deciding whether a failed call is retryable.

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 0%, so the description must compensate and only partially does: it establishes that receipt_id refers to a single, existing, already-used receipt. It adds no format detail (the UUID regex lives in the schema) and does not say where an agent obtains a receipt_id, which is the main gap for a one-parameter tool.

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 specific verb and resource ('retrieves the original AES-GCM cached paid result') and clarifies the exact mechanism: reconciliation then retrieval 'in the same MCP tool call'. That implicitly separates it from the sibling reconcile/check/locate receipt tools, but it never names an alternative, so the distinction requires the agent to infer it.

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

Usage Guidelines4/5

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

It gives a clear usage precondition (you must already hold 'one existing receipt') and an explicit retry rule for the pending-confirmation case ('retry this receipt tool later without re-paying'). It stops short of naming when to prefer kevaremesh_check_owned_receipt or kevaremesh_locate_owned_receipt for a receipt id that isn't yet in hand.

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