Skip to main content
Glama

hands.txt: a human proxy for AI agents

Check your Bitcoin payment

check_payment
Idempotent

Optional. Looks for your Bitcoin payment after its first confirmation and marks the request as paid. Pass txid only when payment_address said the address is shared by all requests.

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": "check_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
txidNoThe transaction id, 64 hex characters. Only for a shared address.
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.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=true; the description is consistent, adding the non-obvious fact that the tool mutates request state ('marks the request as paid') and that it needs a confirmation before it is useful. It does not explain what happens while unconfirmed or what state is returned, which keeps it below 5.

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, front-loaded with the optional status and the core action, then the conditional parameter rule. 'Optional.' is terse to the point of slight ambiguity about optionality of the tool versus the parameter, but there is no filler.

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?

With no output schema and a state-changing tool, the description never indicates what a call returns (pending vs. paid, or an error while unconfirmed), which an agent needs to interpret results. Parameters and preconditions are covered, but that return-side gap leaves it adequate rather than complete.

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 txid and request parameters are already fully documented, including 'Only for a shared address.' The description adds only a small amount: that the shared-address determination comes from payment_address's output. That is marginal value over the schema, so the 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?

The description names a concrete verb and resource ('Looks for your Bitcoin payment') plus the lifecycle stage ('after its first confirmation') and the resulting side effect ('marks the request as paid'). The 'Bitcoin' qualifier implicitly separates it from the sibling check_usdc_payment, though no sibling is named explicitly.

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 precondition for invocation (only meaningful after the first confirmation) and a precise conditional rule for the optional txid, tied to what payment_address reported. It stops short of naming an alternative tool or stating when calling it is pointless, but the usage context is unambiguous.

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