Skip to main content
Glama

Prepare a renewal

renew_names
Read-onlyIdempotent

Prepare renewing .eth names for the user to sign in their own wallet, e.g. 'Renew nick.eth for a year'. Nothing is sent. Anyone can renew any name, while it is registered or in its grace period. Paid in USDC by default, or DAI. Returns the steps, cost, what the account needs, whether it would succeed, 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": {
      "names": "<names>",
      "duration": "<duration>",
      "account": "<account>"
    },
    "name": "renew_names"
  }
}

Input Schema

NameRequiredDescriptionDefault
namesYes1 to 20 .eth names to renew together
accountYesAccount that will sign the transactions: an address (0x…) or an ENS name
durationYes
paymentTokenNoToken to pay with: usdc (default) or dai

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

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

Beyond the readOnly/idempotent/non-destructive annotations, it discloses that nothing is sent on-chain, that permission is unrestricted, the grace-period window, the default payment token with an override, and that the response includes cost, account prerequisites, a success prediction and signing instructions. That is the operational context an agent needs before invoking a transaction-preparation tool.

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 dense sentences, front-loaded with what the tool does and the critical 'nothing is sent' caveat. The final sentence enumerating return values is slightly redundant against the output schema, but it is compact rather than bloated.

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?

For a multi-name transaction-preparation tool the definition covers eligibility, cost, prerequisites and the signing handoff, which is the important surface. The only real omission is any guidance on the `duration` string format, which an agent cannot derive from either the schema or the description.

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 coverage is 75% and the description only echoes the payment-token choice already documented in the enum ('Paid in USDC by default, or DAI'). The `duration` parameter has no description in the schema and no explanation in the description, so its format (e.g. '1 year' vs seconds) remains a genuine gap.

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 states a specific verb and resource — 'Prepare renewing .eth names' — and immediately clarifies the non-obvious mechanism: the user signs in their own wallet and nothing is broadcast. This distinguishes it cleanly from register_name (new registrations) and the list_* discovery siblings.

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 real eligibility conditions: 'Anyone can renew any name, while it is registered or in its grace period,' which tells an agent when a call will be meaningful. It stops short of naming an alternative for names that are unregistered or expired beyond grace, so the agent must infer register_name on its own.

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.