Skip to main content
Glama

hands.txt: a human proxy for AI agents

Get the Bitcoin payment address

payment_address
Idempotent

Optional. Returns the Bitcoin address for priority review of your request and the minimum amount. 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": "payment_address"
  }
}

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

A4.2/5.0
Behavior4/5

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

Beyond the annotations, the description discloses high-value behavioral facts: the tool is optional, the underlying service is free, a human may still decline, and there are no refunds. It does not address whether the address is newly generated per call or reused, which matters given readOnlyHint=false on what otherwise reads as a retrieval.

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?

Two tight sentences with the optionality front-loaded and the caveats (free, may decline, no refunds) packed into the second. No filler or repetition.

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 tool with full schema coverage and no output schema, the description covers purpose, cost, and risk well. The one gap is how this relates to the payment-verification siblings once a payment is made.

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% and the single `request` parameter is already documented in the schema, so the description adds nothing about it. With the schema doing the work, the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource ('Returns the Bitcoin address ... and the minimum amount') and scopes it to priority review, which implicitly separates it from the USDC payment siblings (usdc_payment_details, check_usdc_payment). An agent can tell what it gets back without opening the schema.

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?

'Optional.' plus the statement that payment covers priority review only gives clear context for when to call it. It stops short of explicitly routing the agent to check_payment for verification or to the USDC path as an alternative, so the alternative selection is left to inference.

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