Skip to main content
Glama

hands.txt: a human proxy for AI agents

Get the USDC payment details

usdc_payment_details
Read-only

Optional. Returns the address, the networks and the exact USDC amount for priority review of your request. The amount is unique to the request: its last digits name it. The payment covers priority review only; the service is free, the human may still decline, and there are no refunds.

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>"
    },
    "name": "usdc_payment_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

A3.7/5.0
Behavior4/5

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

Adds substantial context beyond the readOnlyHint/openWorldHint annotations: the amount is unique per request and its last digits encode the request, payment buys priority review only, the service is free, a human may still decline, and there are no refunds. Those are exactly the caveats an agent needs before prompting a user to pay, though it omits what happens on repeat calls or once payment is already made.

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?

Four compact sentences, front-loaded with the 'Optional' status and then the return contents, with each later sentence carrying a distinct caveat. No filler, though 'Optional.' alone is a slightly abrupt lead-in.

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 one-parameter, read-only tool with no output schema, the description covers what comes back and the payment conditions. The remaining gap is the relationship to the sibling payment-checking tools, which the agent must infer.

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 the single parameter is fully documented as either the request URL or its 32-character secret. The description adds no further meaning about that parameter, 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?

States a specific verb and enumerates the exact resource contents returned: address, networks, and the exact USDC amount. It is clearly a read tool for payment instructions. It does not, however, distinguish itself from similarly named siblings such as payment_address or check_usdc_payment.

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?

Opens with 'Optional' and ties the call to 'priority review of your request', which implies the context of use, but never states when to prefer it over check_usdc_payment, check_payment, or payment_address, nor what to do after obtaining the details.

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