Skip to main content
Glama

unarchive_wallet_group

Restores archived cryptocurrency wallet groups to active status for wallet management operations. Use this tool to reactivate wallet groups that were previously archived.

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. Thin wrapper that authenticates and delegates to ArmorWalletAPIClient.unarchive_wallet_group.
    @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 schemas for input validation: UnarchiveWalletGroupRequest (single group) and UnarchiveWalletGroupRequestContainer (list of requests, used by the tool).
    class UnarchiveWalletGroupRequest(BaseModel):
        group: str = Field(description="Name of the group to unarchive")
    
    class RemoveWalletsFromGroupRequest(BaseModel):
        group: str = Field(description="Name of the group to remove wallets from")
        wallet: str = Field(description="List of wallet names to remove from the group")
    
    class TopTrendingTokensRequest(BaseModel):
        time_frame: Literal["5m", "15m", "30m", "1h", "2h", "3h", "4h", "5h", "6h", "12h", "24h"] = Field(default="24h", description="Time frame to get the top trending tokens")
    
    class StakeBalanceResponse(BaseModel):
        total_stake_amount: float = Field(description="Total stake balance in jupSol")
        total_stake_amount_in_usd: float = Field(description="Total stake balance in USD")
    
    
    class RenameWalletRequest(BaseModel):
        wallet: str = Field(description="Name of the wallet to rename")
        new_name: str = Field(description="New name of the wallet")
    
    
    class CandleStickRequest(BaseModel):
        token_address: str = Field(description="Public mint address of the token. To get the address from a token symbol use `get_token_details`")
        time_interval: Literal["1s", "5s", "15s", "1m", "3m", "5m", "15m", "30m", "1h", "2h", "4h", "6h", "8h", "12h", "1d", "3d", "1w", "1mn"] = Field(default="1h", description="Time frame to get the candle sticks. Use larger candle time frames over larger time windows to keep returned candles minimal")
        time_from: str = Field(description="The time from which to start the candle data in ISO 8601 format. Attempt to change this to keep number of candles returned under 64.")
        time_to: Optional[str] = Field(default=None, description="The time to end the candle data in ISO 8601 format. Use only for historic analysis.")
        market_cap: Optional[bool] = Field(default=False, description="Whether to return the marketcap of the token instead of the price")
        
    class PrivateKeyRequest(BaseModel):
        wallet: str = Field(description="Name of the wallet to get the mnemonic or private key for")
        key_type: Literal['PRIVATE_KEY', 'MNEMONIC'] = Field(description="Whether to return the private or mnemonic key")
    
    # ------------------------------
    # Container Models for List Inputs
    # ------------------------------
    
    class RemoveWalletsFromGroupRequestContainer(BaseModel):
        remove_wallets_from_group_requests: List[RemoveWalletsFromGroupRequest]
    
    class AddWalletToGroupRequestContainer(BaseModel):
        add_wallet_to_group_requests: List[AddWalletToGroupRequest]
    
    class CreateWalletRequestContainer(BaseModel):
        create_wallet_requests: List[CreateWalletRequest]
    
    class ArchiveWalletsRequestContainer(BaseModel):
        archive_wallet_requests: List[ArchiveWalletsRequest]
    
    class UnarchiveWalletRequestContainer(BaseModel):
        unarchive_wallet_requests: List[UnarchiveWalletsRequest]
    
    class ArchiveWalletGroupRequestContainer(BaseModel):
        archive_wallet_group_requests: List[ArchiveWalletGroupRequest]
    
    class UnarchiveWalletGroupRequestContainer(BaseModel):
        unarchive_wallet_group_requests: List[UnarchiveWalletGroupRequest]
  • Core implementation in ArmorWalletAPIClient: prepares payload from container and makes POST API call to /wallets/group-unarchive/ endpoint.
    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 model for the response from unarchiving a wallet group.
    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 the full burden of behavioral disclosure. It mentions that it 'Expects a list of group names, returns a list of GroupArchiveOrUnarchiveResponse', which gives some context about input/output, but fails to describe critical behaviors like whether unarchiving is reversible, requires permissions, has side effects, or involves rate limits. This is inadequate for a mutation tool with zero annotation coverage.

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 brief and to the point with two sentences that cover the action and input/output expectations. There's no unnecessary fluff, and it's front-loaded with the main purpose. However, it could be slightly more structured by explicitly separating usage notes from behavioral details.

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 that there's an output schema (which handles return values), no annotations, and low schema coverage, the description is minimally complete. It covers the basic action and input/output but lacks depth on behavioral aspects, error handling, or integration with sibling tools, making it adequate but with clear gaps for a mutation tool.

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?

The description adds minimal semantic value beyond the input schema. It specifies that the tool 'Expects a list of group names', which clarifies the parameter's purpose, but with 0% schema description coverage and 1 parameter, this doesn't fully compensate for the lack of schema details. The baseline is 3 since it provides some context, but more details on the request format would be helpful.

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 tool 'Unarchive wallet groups' which provides a clear verb ('Unarchive') and resource ('wallet groups'), but it doesn't specify what unarchiving entails or differentiate it from sibling tools like 'unarchive_wallets' or 'archive_wallet_group'. The purpose is understandable but lacks specificity about scope or effects.

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 on when to use this tool versus alternatives like 'unarchive_wallets' or 'archive_wallet_group'. The description only states what it does without context about prerequisites, timing, or comparisons to sibling tools, leaving the agent to infer usage scenarios.

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