Skip to main content
Glama

Check a vanity name

check_name
Read-onlyIdempotent

Use when you or your operator want a name on Bitcoin and need to know if it is free and what it costs before buying. Name $21 + network fee, no API key. Checks whether a vanity name (4–12 letters A–Z, not starting with A; trademarked and brand names are blocked) is available and returns the live price: $21 service fee + network fee, in USD and sats. Read-only; does not reserve the name. Buy it with buy_name. A name you hold can also unlock TOKENLOCK-gated sites and APIs (see tokenlock_info).

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe name to check, e.g. SATOSHI.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, but the description adds material context beyond them: the $21 fee plus network fee, no API key required, that no reservation occurs, and admission rules (4–12 letters, no leading A, trademarked/brand names blocked). It does not discuss rate limits or latency, which keeps it from a 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 sentences, front-loaded with the trigger condition and the price. The '$21 + network fee' figure appears twice (opening clause and in the return-value sentence), which is mild redundancy but not enough to obscure the guidance.

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?

With no output schema, the description carries the return-value burden itself, and it does: availability plus live price in USD and sats. Combined with the fee model, name constraints and the pointer to buy_name and tokenlock_info, an agent has everything needed to call and interpret it.

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

Parameters5/5

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

Schema coverage is 100% and there is only one parameter, so the baseline is already high, yet the description still adds meaningful constraints the schema does not encode: the 4–12 letter range, the A–Z alphabet restriction, and the no-leading-A rule tighten a schema that merely allows 1–40 characters. It also notes brand/trademark blocking, which explains likely failure modes for a given name.

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: checks whether a vanity name is available and returns the live price. It also distinguishes itself from the sibling that performs the follow-up action ('Buy it with buy_name'), so an agent can separate checking from purchasing 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Opens with an explicit trigger ('Use when you or your operator want a name on Bitcoin and need to know if it is free and what it costs before buying') and names the follow-up alternative, buy_name. It also states a negative boundary: read-only, does not reserve the name.

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