Skip to main content
Glama

Prepare setting records

set_records
Read-onlyIdempotent

Prepare setting or deleting an ENS name's records for the user to sign in their own wallet, e.g. 'Set alice.eth's twitter to alicedev and its BTC address to bc1…'. Nothing is sent. Text records, addresses by coin and the content hash (website); null deletes a record, clearFirst removes every record first. 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": "set_records"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesENS name as the user wrote it, e.g. nick.eth; normalised by the server (ENSIP-15)
textsNoText records by key, e.g. { url: 'https://…', 'com.github': 'alice' }; null deletes
accountYesAccount that will sign the transactions: an address (0x…) or an ENS name
addressesNoAddresses by coin, e.g. { eth: '0x…', btc: 'bc1…' }; null deletes
clearFirstNoDelete every existing record before writing these
contentHashNoContent hash URI, e.g. ipfs://…; null deletes

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

A3.9/5.0
Behavior4/5

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

Beyond the annotations it discloses that nothing is broadcast, that the response contains steps, a permission verdict, plain signing instructions and unsigned calls — material an agent needs to plan the next step. With readOnlyHint/idempotentHint already covering the safety profile, the remaining gap is minor (e.g. no note on how stale the prepared calls become).

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?

Purpose and the 'Nothing is sent' caveat are front-loaded, and the return-value sentence follows logically. The first sentence is dense and packs an example plus several mechanisms, but nothing is truly waste.

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, full parameter descriptions and annotations present, the description covers the essential behavior for a 6-parameter nested-object tool. It could add a note about prerequisites such as ownership or resolver requirements, which the 'whether the account may make the change' clause only hints at.

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 100% and the schema already documents texts, addresses, contentHash, clearFirst and null-deletes, so the description mostly restates it. It adds only the overall framing that both text records, coin addresses and the content hash are writable in one call, which is baseline value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb-plus-resource ('Prepare setting or deleting an ENS name's records') and a concrete example that makes the effect obvious. It does not explicitly contrast itself with siblings such as get_records or set_primary_name, so it stops short of a 5.

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?

'for the user to sign in their own wallet' plus 'Nothing is sent' clearly establishes the prepare-then-sign context of use. There is no explicit when-not-to-use guidance or named alternative for cases where an already-signed flow is wanted, so it is a 4 rather than 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.