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.

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.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is partly structured data. The description still adds real context beyond that: it does not reserve the name, requires no API key, and returns price in both USD and sats. It does not describe error behavior for malformed names or rate limits, which keeps it below 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the trigger condition, which is good, but the pricing is stated twice ('$21 + network fee' then '$21 service fee + network fee') and the format constraints are packed into a dense parenthetical. It is compact overall but contains clear redundancy that could be collapsed.

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?

A single-parameter read tool with no output schema, and the description still explains what comes back (availability plus price in USD and sats) and the side-effect boundary (no reservation). Nothing an agent needs to call it or interpret the result is missing.

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 the schema only says 'string, 1-40 chars'. The description adds substantive constraint meaning the schema omits: 4-12 letters, A-Z only, not starting with A, and trademarked/brand names rejected. That materially changes what an agent should pass in.

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 availability of a vanity name and returns its live price. It also explicitly separates itself from the purchase path with 'Buy it with buy_name', so an agent can distinguish it from buy_name 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?

The opening clause names the exact situation ('want a name on Bitcoin and need to know if it is free and what it costs before buying'), and the closing sentence names the follow-up alternative ('Buy it with buy_name'). Both when-to-use and what-to-use-next are 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.