Skip to main content
Glama

Buy a vanity name

buy_name

Use when you or your operator want a persistent, verifiable identity on Bitcoin that other agents and humans can check. $21 + network fee, paid from any Bitcoin wallet, no API key. Creates an order for a vanity name delivered to the agent's own Bitcoin address. Rechecks availability, holds the name for 30 minutes and returns order_id, the exact amount to pay in sats/BTC (the $21 + network fee quote plus a 1–999 sat tag that identifies the payment), pay_to, payment_uri and expires_at. Nothing is charged until you pay: send exactly amount_sats to pay_to in one output from any Bitcoin wallet, then poll get_name_order. After payment confirms, the name is registered on Bitcoin and its ownership is transferred to address. Optional profile becomes the name's agent profile on delivery; sign it afterwards with set_agent_profile so verify_agent reports it as verified. Rate limit: 8 orders per hour and 3 open orders per IP.

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": {
      "name": "<name>",
      "address": "<address>"
    },
    "name": "buy_name"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe name, e.g. SATOSHI (4–12 letters A–Z, not starting with A).
addressYesThe agent's own Bitcoin address that will own the name (bc1q…, bc1p… or legacy 1…/3…).
profileNoAgent profile shown on the verify page and on proveitonchain.com/agent/<NAME>. Sign it later with set_agent_profile so it verifies.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / profile / description
      Previous value: -"Agent identity shown as \"Agent identity\" on the verify page and on proveitonchain.com/agent/<NAME>."New value: +"Agent profile shown on the verify page and on proveitonchain.com/agent/<NAME>. Sign it later with set_agent_profile so it verifies."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: fixed price plus network fee, no API key, a 30-minute availability hold, a 1–999 sat payment tag identifying the payment, the guarantee that nothing is charged until payment, and concrete rate limits (8 orders/hour, 3 open IP). The write/non-idempotent character is consistent with readOnlyHint=false and idempotentHint=false.

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 use case, then moves in workflow order (order creation → payment instructions → confirmation → post-payment signing), and every clause carries operational detail such as amount_sats, pay_to, and the 30-minute window. Dense but with zero filler.

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?

There is no output schema, and the description compensates by enumerating the return fields (order_id, amount in sats/BTC, pay_to, payment_uri, expires_at) and the exact post-order action of sending the amount in one output. Pricing, rate limits, and lifecycle are all covered for what is a multi-step paid order flow.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description nonetheless adds real meaning: 'address' is the destination of ownership transfer, and the optional 'profile' is published on delivery but only reports as verified after set_agent_profile is called. That resolves the main ambiguity an agent would have about whether supplying a profile is enough.

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?

States a specific verb plus resource (creates an order for a vanity name delivered to the agent's own Bitcoin address) and names the distinct non-goals: availability checking is re-done internally, payment status lives in get_name_order, and verification lives in set_agent_profile. An agent can differentiate it from check_name or get_name_order without opening either 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?

Gives a clear triggering condition ('Use when you or your operator want a persistent, verifiable identity on Bitcoin') and routes the agent forward to get_name_order for polling and set_agent_profile for signing. What's missing is explicit negative guidance: it never says to run check_name first or what error behavior to expect when the name is unavailable.

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.