Skip to main content
Glama

rename_wallets

Change wallet names in cryptocurrency ecosystems to improve organization and identification. This tool allows users to update wallet labels for better management across multiple chains.

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

  • MCP tool handler function that implements the core logic of the 'rename_wallets' tool by invoking the ArmorWalletAPIClient.rename_wallet method.
    @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)}]
  • The @mcp.tool() decorator registers the 'rename_wallets' function as an MCP tool.
    @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 input schema for a single RenameWalletRequest.
    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 list of RenameWalletRequests, used as input type for the tool.
    class RenameWalletRequestContainer(BaseModel):
        rename_wallet_requests: List[RenameWalletRequest]
  • Helper method in ArmorWalletAPIClient that handles the API call to rename wallets on the backend server.
    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)
Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but fails completely. 'Rename wallets' implies a mutation operation but doesn't disclose whether this requires specific permissions, whether the rename is reversible, what validation occurs, or what happens to wallet identifiers. The mention of returning 'a list' is the only behavioral hint, but insufficient for a mutation tool.

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?

The description is extremely concise (two sentences) but this brevity comes at the cost of being under-specified rather than efficient. The first sentence is tautological, the second provides minimal technical detail. While not wordy, it fails to convey necessary information that would help an agent use the tool correctly.

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 1 parameter (0% schema coverage), no annotations, but with an output schema, the description is severely incomplete. While the output schema may document return values, the description fails to explain the core operation, its behavioral implications, parameter requirements, or usage context. The presence of an output schema doesn't compensate for these fundamental gaps.

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 but provides almost no parameter information. It mentions 'Expects a RenameWalletRequestContainer' which names the parameter but gives no semantic meaning - what this container should contain, what fields are needed, or what 'rename' actually requires. The description adds minimal value beyond what the bare schema structure provides.

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

Purpose2/5

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

The description states 'Rename wallets' which is a tautology that merely restates the tool name without adding specificity. It doesn't clarify what type of wallets (crypto, digital, etc.) or what the rename operation entails. Compared to sibling tools like 'create_wallet' or 'archive_wallets', this provides minimal differentiation beyond the obvious verb.

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

Usage Guidelines1/5

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

The description provides absolutely no guidance on when to use this tool versus alternatives. There's no mention of prerequisites, when renaming is appropriate, what happens to existing wallet references, or how this differs from related operations like creating or archiving wallets. The agent receives zero contextual direction.

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

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/emmaThompson07/armor-crypto-mcp'

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