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. Once delivered, the name also works as a sign-in for TOKENLOCK-gated sites that accept it (start_token_signin). 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.6/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false) by disclosing price ($21 + network fee), that no API key is needed, the 30-minute hold, that nothing is charged until payment, the 1–999 sat payment tag needed for identification, the exact-single-output payment rule, and concrete rate limits (8 orders/hour, 3 open orders/IP). It also spells out what is returned and what happens to the optional profile after delivery.

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?

Front-loads the usage trigger before the mechanics, then walks through order, payment, and delivery in a logical order with no filler. Slightly dense as one paragraph and mildly repetitive ('paid from any Bitcoin wallet' appears twice), but nearly every sentence carries operational weight.

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?

No output schema exists, and the description fully compensates by enumerating returned fields (order_id, amount in sats/BTC, pay_to, payment_uri, expires_at) and the post-payment state. For a 3-parameter, nested-profile, paid mutation tool, nothing an agent needs to call and follow through is missing.

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, but the description adds genuine meaning: it clarifies that the address is the agent's own and becomes the owner, that profile is optional but only verifies after a separate set_agent_profile signing step, and that the name is rechecked at order time. Format constraints on the name itself are left to the schema.

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 and resource ('Creates an order for a vanity name') and immediately distinguishes itself from neighbors by describing the full order lifecycle (recheck availability, 30-minute hold, order_id plus payment fields). An agent can tell this apart from check_name or get_name_order without opening any 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?

Opens with a clear when-to-use clause ('when you or your operator want a persistent, verifiable identity on Bitcoin') and routes the agent to downstream tools (poll get_name_order, sign with set_agent_profile, start_token_signin). It never states a when-not condition, e.g. that check_name alone suffices for a pure availability lookup, so the alternative-selection guidance is implicit rather than explicit.

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