Skip to main content
Glama

Prepare creating a subname

create_subname
Read-onlyIdempotent

Prepare creating a subname for the user to sign in their own wallet, e.g. 'Create pay.alice.eth for 0xabc… with its ETH address set'. Nothing is sent. The account must control the parent name. Can set the owner, records, resolver and expiry; fuses apply to wrapped ENSv1 parents and roles to ENSv2 parents. Returns the steps, whether the account may make the change, plain signing instructions and the unsigned calls.

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": "create_subname"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesFull subname to create, e.g. pay.alice.eth
fusesNoNameWrapper fuses to burn on the subname (wrapped parents); permanent
ownerNoWho will own the subname. Default: the account
rolesNoENSv2 roles the owner gets on the subname
expiryNo
accountYesAccount that will sign the transactions: an address (0x…) or an ENS name
recordsNo
resolverNoown (default): a new resolver for the subname; parent: the parent's resolver; none; or a resolver address

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

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

Beyond the readOnlyHint/idempotent annotations it discloses that nothing is transmitted, that the parent must be controlled by the account, that fuses are permanent and apply to wrapped ENSv1 parents while roles apply to ENSv2 parents, and that the response includes steps, a feasibility check, signing instructions and unsigned calls. The return-value summary overlaps the existing output schema, which keeps this from a 5, but the ENSv1/ENSv2 applicability and irreversibility notes are genuinely additive.

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?

Four sentences, front-loaded with the purpose and example, then the safety caveat, then prerequisites, then capability scope, then return shape. No filler and nothing repeated from the annotations.

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 tool with nested records objects, the description supplies the prerequisite, the non-mutating guarantee, the ENSv1/ENSv2 branching, and a summary of the response. With an output schema already present, nothing an agent needs in order to call this correctly is missing.

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?

The description covers the optional knobs the schema exposes — owner, records, resolver and expiry — and adds a semantic distinction the schema does not make: fuses belong to ENSv1 wrapped parents and roles to ENSv2 parents. With schema coverage at 75% and only expiry left undocumented in both places, this is meaningfully above baseline.

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 names a specific verb and resource ('Prepare creating a subname') and immediately grounds it with a concrete example ('Create pay.alice.eth for 0xabc… with its ETH address set'). It also distinguishes the operation from a direct write by stating 'Nothing is sent' and that the output is unsigned calls for the user to sign, which separates it from sibling mutation tools like update_subname or remove_subname.

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?

It gives a clear precondition ('The account must control the parent name') and describes the intended flow (prepare, then the user signs in their own wallet), which tells an agent when this tool is the right entry point. It stops short of naming alternatives or explicit when-not-to-use cases, so it is clear context rather than full routing guidance.

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.