Skip to main content
Glama

ArcHive

arc_verify_receipt

Checks an inference receipt the way SessionPay.settle does: the session's locked enclave, active at the anchor block under its operator, locked model, growing cumulative total; and what the settlement would pay.

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": "<receipt>",
      "signature": "<signature>"
    },
    "name": "arc_verify_receipt"
  }
}

Input Schema

NameRequiredDescriptionDefault
receiptYesthe receipt signed by the enclave, as it returns it (fields as decimal and hex strings)
signatureYesthe enclave's EIP-712 signature: 0x + 130 hex (65 bytes)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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 behavioral burden. It does disclose the validation rules and that it mirrors SessionPay.settle semantics, which is genuinely useful, but it never states whether the call is read-only or has side effects, what happens when verification fails (throws vs. returns a negative result), or that it depends on live chain state at the anchor block. For a verification tool with zero annotation coverage these are material omissions.

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?

It is a single front-loaded sentence that leads with the verb and packs the validation list into a semicolon sequence without filler. The phrasing is dense and jargon-dependent ('the way SessionPay.settle does') for readers who do not know that contract, but nothing is redundant.

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 nested-schema verification tool with no output schema, the description should indicate the shape of a pass/fail outcome and whether the result includes a payout figure; it only gestures at 'what the settlement would pay'. Combined with the absence of annotations, an agent knows the validation criteria but not the response contract or failure mode, which is a meaningful gap for a 100%-coverage but structurally complex input.

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%, including per-field formats for every receipt member and the 65-byte EIP-712 signature, so the schema does the heavy lifting. The description adds the framing that the receipt is 'the way SessionPay.settle' consumes it but contributes no additional meaning about the two top-level parameters, so the baseline of 3 applies.

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: it 'Checks an inference receipt' and enumerates exactly what is validated (locked enclave, operator, anchor block, locked model, cumulative total). It does not name or distinguish itself from plausible siblings like arc_session_status or arc_enclave_status, so an agent must infer that this is the receipt-level check rather than a session/enclave state lookup.

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?

Usage is only implied through the reference to 'what the settlement would pay', suggesting this is a pre-settlement dry run. There is no explicit when-to-use, no when-not-to-use, and no named alternative for agents who want session or enclave state instead, leaving the agent to infer the sequencing.

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.