Skip to main content
Glama

Prepare a transfer

transfer_name
Read-onlyIdempotent

Prepare transferring an ENS name to another address for the user to sign in their own wallet, e.g. 'Send alice.eth to bob.eth'. Nothing is sent. The recipient gets full control; double-check the address. For unwrapped ENSv1 .eth names, role: registrant moves only the registration and keeps the manager.

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>",
      "account": "<account>",
      "to": "<to>"
    },
    "name": "transfer_name"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesRecipient: an address or an ENS name
nameYesENS name as the user wrote it, e.g. nick.eth; normalised by the server (ENSIP-15)
roleNoowner (default): everything; registrant: only the .eth registration (ENSv1)
accountYesAccount that will sign the transactions: an address (0x…) or an ENS name
recordsNoENSv2: keep (default) the sender's access to the name's records, or hand it over

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

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

Adds real behavioral context beyond the annotations: 'Nothing is sent' reinforces readOnlyHint, and the warning that the recipient gets full control discloses the consequence of the state change being prepared. It also explains the role-specific effect (registrant moves only the registration and keeps the manager), which annotations cannot express. It does not mention chain coverage, expiry, or how the prepared payload should be submitted.

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 compact sentences, front-loaded with the action and immediately followed by the safety-critical 'Nothing is sent'. The quoted example is slightly decorative but cheap and aids intent matching; nothing is redundant with the schema.

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 an output schema present and full parameter documentation, the description only needs to carry intent, safety, and role semantics — all of which it covers. An agent has everything required to decide and call 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?

Schema coverage is 100%, so the baseline is 3, but the description earns more by clarifying what 'registrant' actually preserves ('keeps the manager') and by scoping that behavior to unwrapped ENSv1 .eth names. That adds meaning beyond the enum text 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 transferring an ENS name to another address') plus the crucial qualifier that the transaction is unsigned and returned for the user to sign. The illustrative example 'Send alice.eth to bob.eth' immediately anchors what kind of request maps to this tool, and no sibling in the catalog does prepared-transfer construction.

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?

Gives clear conditions for use (prepare, do not send; the user signs in their own wallet) and a caution to double-check the recipient address. It does not enumerate when to prefer this over an alternative path, but among the listed siblings there is no competing execution tool, so the omission is minor.

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.