Skip to main content
Glama

Prepare removing a subname

remove_subname
Read-onlyIdempotent

Prepare removing a subname for the user to sign in their own wallet, e.g. 'Delete old.alice.eth'. Nothing is sent. The account must control the parent 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": "remove_subname"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesFull subname, e.g. old.alice.eth
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/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds meaningful context beyond them: no transaction is broadcast ('Nothing is sent'), signing happens in the user's own wallet, and an authorization requirement (control of the parent name) applies. This resolves the potential confusion of a destructive-looking operation carrying destructiveHint=false.

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?

Three short sentences, front-loaded with the action and example, followed by the two facts that matter most (nothing is sent, parent-name control required). No filler.

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?

An output schema exists so return values need no explanation, and both required parameters are covered by the schema plus description. The workflow (prepare → user signs) is conveyed; slightly more detail on what the caller does with the prepared result would make it complete.

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 description coverage is 100%, so both parameters are fully documented in the schema. The description only reinforces the 'name' parameter with the example 'old.alice.eth' and ties 'account' to the signing role; it adds little beyond structured data, so baseline 3 applies.

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?

States a specific verb and resource ('Prepare removing a subname') and clarifies the mode of operation ('for the user to sign in their own wallet'), so an agent can tell this is a transaction-building step rather than an executed deletion. It does not explicitly contrast with siblings like update_subname or create_subname, which keeps it from 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?

Provides concrete usage context: it is for the user to sign in their own wallet, nothing is broadcast, and the calling account must control the parent name. These are real prerequisites, though there is no explicit statement about when to prefer this over other mutation paths.

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.