Skip to main content
Glama

Prepare a registration

register_name
Read-onlyIdempotent

Prepare registering .eth names for the user to sign in their own wallet, e.g. 'Register alice.eth for 2 years'. Nothing is sent. Registration takes two signatures at least a minute apart (commit, then register) and is paid in USDC by default, or DAI. Can also set records and make the name the account's primary name. Returns the steps, cost, what the account needs, whether it would succeed, plain signing instructions and the unsigned calls. Check availability and price first with check_availability.

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>",
      "duration": "<duration>",
      "account": "<account>"
    },
    "name": "register_name"
  }
}

Input Schema

NameRequiredDescriptionDefault
namesYes1 to 20 .eth names to register together
ownerNoWho will own the names. Default: the account
accountYesAccount that will sign the transactions: an address (0x…) or an ENS name
recordsNoRecords to set on every name
durationYes
resolverNoown (default): a new resolver for each name; shared: the account's shared resolver, as the ENS app uses; none; or a resolver address
paymentTokenNoToken to pay with: usdc (default) or dai
setPrimaryNameNoMake the (single) name the account's primary name

Output Schema

NameRequiredDescriptionDefault
costYes
planYesHandle of this plan for get_plan; pass it back unchanged
callsYesUnsigned calls, in order, for the account's wallet
chainYes
stepsYes
issuesYesWhy a checked step would fail
accountYes
deploysNoContracts the plan deploys, at addresses known in advance
signingYesHow to sign the steps, in plain words
summaryYes
warningsYes
willSucceedYesWhether the steps that can be checked now would succeed if signed now
requirementsYesWhat the account needs before signing, e.g. a token balance

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Adds substantial context the annotations cannot convey: no transaction is broadcast, registration requires two signatures at least a minute apart (commit then register), and payment defaults to USDC with DAI as an option. The only friction is that readOnlyHint=true could confuse an agent given the word 'registering', and the description resolves that with 'Nothing is sent' — a good save, though it could be stated even earlier and more explicitly as 'no on-chain write occurs'.

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-loaded with purpose and the 'Nothing is sent' safety fact, then prerequisites, then return shape — a sensible order. The middle sentences are long and multiply-claused, but each carries information an agent needs, so there is little fat to trim.

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?

For an 8-parameter, nested-object tool that prepares a multi-signature flow, the description covers the timing constraint, payment options, record and primary-name side effects, the prerequisite check, and the shape of the response. With an output schema present it need not detail return fields, and the brief mention of steps/cost/unsigned calls is sufficient orientation.

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

Parameters3/5

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

Schema description coverage is 88%, so the schema already carries most parameter meaning. The description adds value by surfacing defaults (USDC payment, primary-name option, record setting) and the duration example 'for 2 years', but it does not explain the resolver modes or how the single-name constraint on setPrimaryName interacts with the names array (that constraint lives only in 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 ('Prepare registering .eth names for the user to sign in their own wallet') with a concrete example, and immediately sets this apart from the write-path siblings by saying nothing is sent. An agent can distinguish it from check_availability and from actual registration flows 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?

Explicitly routes the agent to a prerequisite alternative: 'Check availability and price first with check_availability.' It also implies the correct usage context (user signs in their own wallet, this tool only prepares). It stops short of naming when-not-to-use cases, such as renewals or transfers handled by siblings, but the core routing guidance is unambiguous.

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.