Skip to main content
Glama
armorwallet
by armorwallet

add_wallets_to_group

Organize crypto wallets efficiently by adding multiple wallets to a specified group using this tool. Simplify blockchain management for structured operations and strategies.

Instructions

Add wallets to a specified group.

Expects the group name and a list of wallet names, returns a list of AddWalletToGroupResponse.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
add_wallet_to_group_requestsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The MCP tool handler function for 'add_wallets_to_group', decorated with @mcp.tool() which also serves as registration. It calls the armor_client to perform the action.
    @mcp.tool()
    async def add_wallets_to_group(add_wallet_to_group_requests: AddWalletToGroupRequestContainer) -> List[AddWalletToGroupResponse]:
        """
        Add wallets to a specified group.
        
        Expects the group name and a list of wallet names, returns a list of AddWalletToGroupResponse.
        """
        if not armor_client:
            return [{"error": "Not logged in"}]
        try:
            result: List[AddWalletToGroupResponse] = await armor_client.add_wallets_to_group(add_wallet_to_group_requests)
            return result
        except Exception as e:
            return [{"error": str(e)}]
  • Input schema container for the tool, wrapping a list of AddWalletToGroupRequest.
    class AddWalletToGroupRequestContainer(BaseModel):
        add_wallet_to_group_requests: List[AddWalletToGroupRequest]
  • Inner input schema model defining group and wallet names.
    class AddWalletToGroupRequest(BaseModel):
        group: str = Field(description="Name of the group to add wallets to")
        wallet: str = Field(description="Name of the wallet to add to the group")
  • Output schema model for the tool response.
    class AddWalletToGroupResponse(BaseModel):
        wallet_name: str = Field(description="name of the wallet to add to the group")
        group_name: str = Field(description="name of the group to add the wallet to")
        message: str = Field(description="message of the operation showing if wallet was added to the group")
  • Helper function in ArmorWalletAPIClient that performs the actual API call to add wallets to group.
    async def add_wallets_to_group(self, data: AddWalletToGroupRequestContainer) -> List[AddWalletToGroupResponse]:
        """Add wallets to a specific group."""
        # payload = json.dumps([{"wallet": wallet_name, "group": data.group_name} for wallet_name in data.wallet_names])
        payload = data.model_dump(exclude_none=True)['add_wallet_to_group_requests']
        return await self._api_call("POST", "wallets/add-wallet-to-group/", payload)
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the operation ('Add wallets') and return type ('AddWalletToGroupResponse'), but doesn't address critical behavioral aspects like whether this is idempotent, what happens if wallets are already in the group, permission requirements, error conditions, or rate limits. The description provides minimal behavioral context beyond the basic operation.

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?

The description is appropriately concise with two sentences that cover the basic operation and return type. It's front-loaded with the core purpose. While efficient, it could benefit from slightly more detail given the complete lack of annotations and schema descriptions.

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

Completeness3/5

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

Given the mutation nature of the tool (adding to groups), no annotations, 0% schema description coverage, but presence of an output schema, the description is minimally adequate. It states what the tool does and what it returns, but doesn't provide enough context about behavioral implications, error handling, or parameter details that would be crucial for safe invocation.

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%, meaning the schema provides no parameter descriptions. The description mentions 'group name and a list of wallet names', which clarifies the expected input structure, but doesn't explain format constraints, validation rules, or the relationship between the described parameters and the actual schema structure (which nests them in an array container). This partial compensation is insufficient given the complete lack of schema documentation.

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 clearly states the action ('Add wallets') and target resource ('to a specified group'), providing a specific verb+resource combination. However, it doesn't distinguish this tool from its sibling 'remove_wallets_from_group' beyond the obvious directionality, missing explicit differentiation about when each should be used.

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?

The description provides no guidance on when to use this tool versus alternatives like 'create_groups' or 'remove_wallets_from_group'. It doesn't mention prerequisites (e.g., group must exist), exclusions, or appropriate contexts, leaving the agent to infer usage from the tool name alone.

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