Skip to main content
Glama

update_account

Destructive

Set the configured wallet's account name once, optionally for a specific network, to label and identify the account.

Instructions

Update the name of the configured wallet's account. Can only be set once.

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": {
      "accountName": "<accountName>"
    },
    "name": "update_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
networkNoNetwork name. Defaults to mainnet.
accountNameYesNew account name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.9
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.1.7

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag destructive=true and idempotent=false, but the description earns credit by explaining why: the name can only be set once, making the operation irreversible. It also clarifies that the target is the configured wallet rather than an arbitrary address. It stops short of saying what error or state results from a second attempt.

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?

Two short sentences, zero filler, with the core action stated first and the critical one-time constraint immediately after. Nothing is redundant with the title or schema.

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 two-parameter tool with full schema coverage, annotations, and no output schema, the description supplies what the structured fields cannot: the one-time nature and the implicit targeting of the configured wallet. Only the failure behavior on a repeat call is left unstated.

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%, so both parameters are already documented, and the baseline is 3. The description's phrase 'configured wallet's account' usefully implies there is no account-address parameter, but it adds no detail about the network parameter or the account name's format and constraints.

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 states a specific verb and resource ('Update the name of the configured wallet's account') and scopes it to the configured wallet, which implicitly separates it from address-taking siblings like account_permission_update or create_account. It does not explicitly name a sibling it should be preferred over, 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The sentence 'Can only be set once' is a real precondition that tells the agent this is a one-shot operation, not a routine rename. However, there is no guidance on what to do instead if the name is already set, nor any mention of required permissions or prerequisites, so usage is only implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools