Skip to main content
Glama

Prepare changing a subname

update_subname
Read-onlyIdempotent

Prepare changing an existing subname for the user to sign in their own wallet: a new owner (ENSv1), resolver or later expiry, e.g. 'Point pay.alice.eth at the public resolver'. Nothing is sent. To change its records use set_records; to transfer an ENSv2 subname use transfer_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>",
      "account": "<account>"
    },
    "name": "update_subname"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesFull subname, e.g. pay.alice.eth
ownerNoNew owner (ENSv1 only)
expiryNo
accountYesAccount that will sign the transactions: an address (0x…) or an ENS name
resolverNoNew resolver address, or none to remove it

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

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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds the crucial interpretation: this is a prepare-only step whose output the user signs in their own wallet, so no state changes occur. It does not cover edge behavior such as whether expiry must exceed the current expiry or how owner changes differ between ENSv1 and ENSv2 beyond a parenthetical.

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?

Two tight sentences front-load the purpose, follow with the example, then the non-mutating guarantee and the sibling routing. Every clause carries information; nothing is restated from the name or title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 annotations covering the safety profile, the description only needs to establish intent and routing, which it does. A minor gap is that it does not say what the prepared artifact is (calldata, transaction request) or what the caller should do with it after preparation.

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 80%, so the schema does most of the work, but the description adds meaning the schema lacks: 'later expiry' clarifies the expiry parameter is an extension rather than an arbitrary set, and 'a new owner (ENSv1)' scopes the owner parameter. It does not clarify the resolver 'none' sentinel, which the schema handles.

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 changing an existing subname"), enumerates the three things it can change (owner, resolver, expiry), and gives a concrete example. It also names the siblings it is not (set_records, transfer_name), so an agent can distinguish it without opening the 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?

Explicitly says "Nothing is sent" and routes the agent to set_records for record changes and transfer_name for ENSv2 transfers. Both the when-to-use and the when-to-use-something-else conditions are stated, not inferred.

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.