Skip to main content
Glama

hands.txt: a human proxy for AI agents

Check your USDC payment

check_usdc_payment
Idempotent

Optional. Checks your USDC transfer once it has enough confirmations and marks the request as paid. Name the network you paid on and the transaction hash.

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": {
      "request": "<request>",
      "network": "<network>",
      "tx": "<tx>"
    },
    "name": "check_usdc_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
txYesThe transaction hash: 0x and 64 hex characters.
networkYesThe network the transfer was sent on.
requestYesThe URL of your request, as create_request returned it, or just its 32-character secret.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Adds real context beyond the annotations by disclosing that the call requires sufficient confirmations and that it mutates state by marking the request as paid, which explains the readOnlyHint=false / non-destructive profile. It does not disclose what happens when confirmations are insufficient (error? pending status?), how many confirmations count as 'enough', or whether the check is synchronous, so the behavioral picture is only partly filled in.

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 short sentences with no filler, and the core purpose plus the confirmation precondition are front-loaded. The leading 'Optional.' is the only weak element — it is ambiguous about what exactly is optional without further explanation.

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 mutating, open-world, idempotent tool with three fully documented required parameters and no output schema, the definition covers how to call it and roughly when. It leaves out the outcome when confirmations are insufficient and any notion of return value or pending state, which an agent needs to handle the call's failure modes.

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 the tx hash format, the ethereum/base enum, and the request URL-or-secret are already fully documented. The description's closing sentence ('name the network you paid on and the transaction hash') only restates the schema and adds no new meaning; the unmentioned 'request' parameter is nonetheless covered by the schema. Baseline 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?

States a specific verb (checks) and a specific resource (your USDC transfer) plus the side effect of marking the request paid, which is enough to separate it from the generic check_payment sibling by scope. It does not explicitly contrast itself with usdc_payment_details, so the differentiation is implied by the name rather than spelled out.

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?

Gives a timing condition ('once it has enough confirmations') which tells the agent when the call is valid, and labels the tool 'Optional.' However, it never says what to do instead — e.g. whether check_payment or usdc_payment_details is the alternative before confirmations land — and 'Optional' is left unexplained.

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