Skip to main content
Glama

Check name availability

check_availability
Read-onlyIdempotent

Check whether .eth names can be registered and what they cost, e.g. 'Is alice.eth available?'. Takes up to 50 names; available ones come with their price for the duration (1 year by default), including any premium on a recently expired name. For who holds a taken name, use get_name_details; to register one, use register_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": {
      "names": "<names>"
    },
    "name": "check_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
namesYes1 to 50 ENS names as the user wrote them
durationNo
paymentTokenNoToken to pay with: usdc (default) or dai

Output Schema

NameRequiredDescriptionDefault
resultsYes
durationYes

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 carry readOnly, idempotent, openWorld and non-destructive, so the description's job is to add semantics beyond them, which it does: batching up to 50 names, price returned for a default 1-year duration, and a premium applied to recently expired names. It stops short of noting rate limits or partial-failure behaviour for a batch, so it is strong but not exhaustive.

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?

Three front-loaded sentences: what it does, what it returns and the batch limit, then the routing to alternatives. The inline example of a natural-language question earns its place by clarifying intent.

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?

An output schema exists, so return values need not be enumerated, and the description still covers the one return detail that matters (price and premium). Combined with explicit sibling routing, an agent has everything needed to call it correctly.

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?

At 67% schema coverage the description still contributes: it explains that pricing is tied to the duration with a 1-year default (the schema leaves duration undocumented) and that premiums affect the returned price. The names cap and payment token usage are already documented in the schema, so the description correctly does not repeat them in detail.

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 gives a specific verb and resource plus the question it answers ('Is alice.eth available?'), and it explicitly contrasts itself with get_name_details and register_name, so the agent can pick it 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 Guidelines5/5

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

It names both alternatives and the exact condition that should route to each: get_name_details for the holder of a taken name and register_name to actually register. Nothing 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.