Skip to main content
Glama

check_report_payment

Idempotent

Hand the Check payment to the server once it is mined, by the Check id. The server reads it on-chain (the payer the charge names signed it, the network USDC reached the fee wallet, at least the price, after the charge, the mark) and reserves the hash for this Check only. 201 with check.status paid: the credit exists. analysis_payment_pending (409): not mined yet, call again in a few seconds. analysis_payment_rejected (400, details.reason): this transaction does not pay this Check. tx_already_used (409): the hash already paid something else. check_not_found (404): no Check has this id. Mined after the charge's 30 minutes it still credits by the price of now on the networks it covers (lateCharge true, check.paidNetworks may be fewer); check_charge_expired (409) only when it covers none. check_credit_limit (409) and payer_blocked (403) are checked again here; nothing is reserved, so the same hash reported later still counts. Repeating the same hash is safe; never pay again.

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": {
      "checkId": "<checkId>",
      "txHash": "<txHash>"
    },
    "name": "check_report_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
txHashYesThe EVM transaction hash or the Solana signature.
checkIdYesThe Check id from check_charge (CHK-...). It is the capability of this Check: keep it, and keep it private.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / properties / access
      Removed value: -{
      -  "description": "The Check access of this payer from check_access (vca_...). Secret: it reads and spends this payer's credits.",
      -  "type": "string"
      -}
    • changedInput schema / properties / checkId / description
      Previous value: -"check.id from check_charge (CHK-...)."New value: +"The Check id from check_charge (CHK-...). It is the capability of this Check: keep it, and keep it private."
    • removedInput schema / properties / payer
      Removed value: -{
      -  "description": "The wallet that paid.",
      -  "type": "string"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "checkId",
      -  "txHash",
      -  "payer",
      -  "access"
      -]New value: +[
      +  "checkId",
      +  "txHash"
      +]
  2. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only declare non-read-only, idempotent, open-world and non-destructive; the description adds the substantive behavior: on-chain verification of signer, USDC arrival, amount and timing, hash reservation for this Check only, full error taxonomy (pending/rejected/tx_already_used/not_found/expired/credit_limit/payer_blocked), late-charge crediting, and idempotent re-reporting. This is materially richer than the structured fields and consistent with idempotentHint=true.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the action and precondition, then enumerates outcomes in short labeled clauses (status code plus reason), which is exactly the structure an agent needs to branch on. Dense but no sentence lacks decision value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and a high-stakes verification flow, the description still supplies success semantics (201 paid means credit exists), every failure mode with codes, and edge-case crediting rules. An agent has enough to call it correctly and interpret any response.

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% and both parameters are already documented, including that txHash may be an EVM hash or Solana signature and that checkId comes from check_charge. The description reinforces that the same hash may be re-reported later, but adds little new syntax or meaning beyond the schema, so the baseline 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?

"Hand the Check payment to the server once it is mined, by the Check id" gives a specific verb, resource and precondition, and the closing "never pay again" implicitly separates reporting from charging/paying. It does not name a sibling tool outright, so the differentiation is inferred rather than stated.

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?

The precondition ("once it is mined") and the retry path ("not mined yet, call again in a few seconds") tell the agent exactly when to call and what to do on a 409 pending. It stops short of explicit when-not guidance beyond the strong "never pay again" warning, so no alternative tool is named.

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