Skip to main content
Glama
armorwallet
by armorwallet

unarchive_wallet_group

Restore archived wallet groups on Armor Crypto MCP by specifying group names. Returns a response confirming the unarchiving process for each group.

Instructions

Unarchive wallet groups.

Expects a list of group names, returns a list of GroupArchiveOrUnarchiveResponse.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
unarchive_wallet_group_requestsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • MCP tool handler and registration for 'unarchive_wallet_group'. This is the entry point for the tool, decorated with @mcp.tool(), handling input validation via type hints and delegating to the Armor client.
    @mcp.tool()
    async def unarchive_wallet_group(unarchive_wallet_group_requests: UnarchiveWalletGroupRequestContainer) -> List[GroupArchiveOrUnarchiveResponse]:
        """
        Unarchive wallet groups.
        
        Expects a list of group names, returns a list of GroupArchiveOrUnarchiveResponse.
        """
        if not armor_client:
            return [{"error": "Not logged in"}]
        try:
            result: List[GroupArchiveOrUnarchiveResponse] = await armor_client.unarchive_wallet_group(unarchive_wallet_group_requests)
            return result
        except Exception as e:
            return [{"error": str(e)}]
  • Pydantic schema for individual unarchive wallet group request, defining the 'group' field.
    class UnarchiveWalletGroupRequest(BaseModel):
        group: str = Field(description="Name of the group to unarchive")
  • Pydantic container schema for the tool input, wrapping a list of UnarchiveWalletGroupRequest objects.
    class UnarchiveWalletGroupRequestContainer(BaseModel):
        unarchive_wallet_group_requests: List[UnarchiveWalletGroupRequest]
  • Helper method in ArmorWalletAPIClient that prepares the payload and makes the POST API call to unarchive wallet groups.
    async def unarchive_wallet_group(self, data: UnarchiveWalletGroupRequestContainer) -> List[GroupArchiveOrUnarchiveResponse]:
        """Unarchive the specified wallet groups."""
        # payload = json.dumps([{"group": group_name} for group_name in data.group_names])
        payload = data.model_dump(exclude_none=True)['unarchive_wallet_group_requests']
        return await self._api_call("POST", "wallets/group-unarchive/", payload)
  • Pydantic schema for the output response, containing the group name.
    group: str = Field(description="name of the group")
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 mentions the input format ('list of group names') and return type ('GroupArchiveOrUnarchiveResponse'), but doesn't describe what unarchiving actually does, whether it requires specific permissions, if it's reversible, or potential side effects. For a mutation tool with zero annotation coverage, this is insufficient.

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. The first states the purpose, the second covers input/output expectations. There's no wasted text, though it could be more informative while maintaining brevity.

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 this is a mutation tool with no annotations, 0% schema description coverage, but with an output schema (which handles return values), the description is minimally complete. It covers basic purpose and I/O format but lacks crucial behavioral context about what unarchiving entails, making it inadequate for safe agent operation.

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 'list of group names' which maps to the single parameter, but doesn't explain what constitutes a valid group name, format requirements, or constraints. The description adds minimal value beyond what's inferable from the parameter name itself.

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 verb ('unarchive') and resource ('wallet groups'), which provides basic purpose. However, it doesn't distinguish this tool from its sibling 'unarchive_wallets' or explain what 'unarchive' means operationally. The description is vague about the actual effect of unarchiving.

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 is provided about when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., groups must be archived first), when not to use it, or how it differs from 'unarchive_wallets'. The agent receives no contextual usage information.

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