Skip to main content
Glama

Prepare setting a primary name

set_primary_name
Read-onlyIdempotent

Prepare setting the primary ENS name of an account (reverse record) for the user to sign in their own wallet, e.g. 'Make alice.eth my primary name'. Nothing is sent. The name should resolve to the account, or apps will not show it; the result warns when it does not. Set coin for a primary name on an L2 such as base or op.

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

Input Schema

NameRequiredDescriptionDefault
coinNoChain of the primary name, e.g. base or op. Default: eth
nameYesENS name as the user wrote it, e.g. nick.eth; normalised by the server (ENSIP-15)
accountYesAccount that will sign the transactions: an address (0x…) or an ENS 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.6/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: 'Nothing is sent' explains why a set-style operation carries readOnlyHint, the user must sign in their own wallet, and the name must resolve to the account or apps will not display it. It also discloses that the result surfaces a warning when that precondition fails, which the structured fields do not.

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 the prepare-only nature and the user-signing flow, with no padding. The final clause about coin is a compressed fragment, which sacrifices a little readability for brevity.

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 a 3-parameter prepare tool with an output schema and annotations, all the agent-critical facts are present: nothing is executed, the user signs, the reverse-record precondition, and L2 coin handling. Return-value details are correctly left to the output schema.

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 adds semantic constraints: the name must resolve to the account, and the coin parameter is specifically for L2 primary names such as base or op. This goes slightly beyond the schema's own examples.

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 ('setting the primary ENS name of an account (reverse record)') and clarifies upfront that it only prepares a transaction ('for the user to sign in their own wallet'). An agent can immediately distinguish this from the read-side sibling get_primary_name.

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 a concrete usage example ('Make alice.eth my primary name') and a specific conditional ('Set coin for a primary name on an L2 such as base or op'). It does not explicitly name alternatives or state when not to use it, so it stops short of a 5.

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.