Skip to main content
Glama
armorwallet
by armorwallet

rename_wallets

Enables renaming of wallets by providing a list of wallet names and their new names, streamlining wallet management within the Armor Crypto MCP server.

Instructions

Rename wallets.

Expects a RenameWalletRequestContainer, returns a list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rename_wallet_requestsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main MCP tool handler function for 'rename_wallets', decorated with @mcp.tool() for registration, performs login check and delegates to armor_client.rename_wallet.
    @mcp.tool()
    async def rename_wallets(rename_wallet_requests: RenameWalletRequestContainer) -> List:
        """
        Rename wallets.
        
        Expects a RenameWalletRequestContainer, returns a list.
        """
        if not armor_client:
            return [{"error": "Not logged in"}]
        try:
            result: List = await armor_client.rename_wallet(rename_wallet_requests)
            return result
        except Exception as e:
            return [{"error": str(e)}]
  • Pydantic model defining the structure for a single wallet rename request (wallet name and new name).
    class RenameWalletRequest(BaseModel):
        wallet: str = Field(description="Name of the wallet to rename")
        new_name: str = Field(description="New name of the wallet")
  • Pydantic container model for the tool input: a list of RenameWalletRequest objects, used as type hint in the handler.
    class RenameWalletRequestContainer(BaseModel):
        rename_wallet_requests: List[RenameWalletRequest]
  • Supporting method in ArmorWalletAPIClient that serializes the input and makes the POST API call to /wallets/rename/ endpoint.
    async def rename_wallet(self, data: RenameWalletRequestContainer) -> List:
        """Rename a wallet."""
        payload = data.model_dump(exclude_none=True)['rename_wallet_requests']
        return await self._api_call("POST", "wallets/rename/", payload)
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the tool renames wallets and returns a list, but doesn't disclose critical behavioral traits like whether renaming requires specific permissions, if names must be unique, what happens on failure, or if the operation is reversible. For a mutation tool with zero annotation coverage, this is inadequate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with zero waste, but under-specified. The first sentence states the purpose, the second hints at input/output, but it's too brief to be fully helpful. It's concise but lacks necessary detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no annotations, 0% schema description coverage, and multiple sibling tools, the description is incomplete. It doesn't address permissions, error handling, batch behavior, or how to interpret the returned list. The output schema exists but isn't referenced, leaving gaps in understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It mentions 'RenameWalletRequestContainer' and 'returns a list' but doesn't explain what parameters are needed, their formats, or the structure of requests. The description adds minimal value beyond the schema's parameter names.

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

Purpose3/5

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

The description states the action ('Rename wallets') which is a clear verb+resource combination, but it doesn't specify scope or differentiate from siblings like 'create_wallet' or 'archive_wallets'. It's vague about whether this renames individual wallets or batches.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like 'create_wallet' for new wallets or 'archive_wallets' for removal. The description doesn't mention prerequisites, constraints, or appropriate contexts for renaming.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/armorwallet/armor-crypto-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server