Skip to main content
Glama

archive_wallet_group

Archive cryptocurrency wallet groups to organize and manage digital asset holdings within the Armor Crypto MCP server environment.

Instructions

Archive wallet groups.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
archive_wallet_group_requestsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • MCP tool handler that executes the archive_wallet_group tool by calling the armor_client method with validated input.
    @mcp.tool()
    async def archive_wallet_group(archive_wallet_group_requests: ArchiveWalletGroupRequestContainer) -> List[GroupArchiveOrUnarchiveResponse]:
        """
        Archive 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.archive_wallet_group(archive_wallet_group_requests)
            return result
        except Exception as e:
            return [{"error": str(e)}]
  • Pydantic model for single ArchiveWalletGroupRequest defining the group name.
    class ArchiveWalletGroupRequest(BaseModel):
        group: str = Field(description="Name of the group to archive")
  • Pydantic container model for list of ArchiveWalletGroupRequest used as input schema for the tool.
    class ArchiveWalletGroupRequestContainer(BaseModel):
        archive_wallet_group_requests: List[ArchiveWalletGroupRequest]
  • Helper method in ArmorWalletAPIClient that performs the actual API call to archive wallet groups.
    async def archive_wallet_group(self, data: ArchiveWalletGroupRequestContainer) -> List[GroupArchiveOrUnarchiveResponse]:
        """Archive the specified wallet groups."""
        # payload = json.dumps([{"group": group_name} for group_name in data.group_names])
        payload = data.model_dump(exclude_none=True)['archive_wallet_group_requests']
        return await self._api_call("POST", "wallets/group-archive/", payload)
  • Pydantic model for the response of archiving/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' and 'returns a list of GroupArchiveOrUnarchiveResponse', which gives basic input/output context. However, it fails to disclose critical behavioral traits: whether archiving is reversible, if it requires specific permissions, what happens to wallets in archived groups, or any rate limits or side effects. 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 very concise with two sentences that are front-loaded: the first states the purpose, and the second covers input and output. There's no wasted text, but it could benefit from slightly more detail to improve clarity without sacrificing 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 the complexity of a mutation tool with no annotations and 0% schema coverage, the description is incomplete. It mentions the return type ('GroupArchiveOrUnarchiveResponse'), which aligns with the presence of an output schema, reducing the need to explain return values. However, it lacks essential context such as error conditions, idempotency, or effects on related resources, making it minimally adequate but with clear gaps for safe and effective use.

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 semantics beyond the input schema: it indicates the parameter is a 'list of group names', which clarifies the expected content of 'archive_wallet_group_requests'. However, with 0% schema description coverage, the schema provides no details about the parameter structure or constraints. The description doesn't compensate fully—it doesn't explain the format of group names, any validation rules, or the container structure—leaving significant gaps in parameter understanding.

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 ('Archive') and resource ('wallet groups'), making the purpose understandable. However, it doesn't differentiate from the sibling 'unarchive_wallet_group' tool, which performs the opposite operation, or from 'archive_wallets' which archives individual wallets rather than groups.

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 'unarchive_wallet_group' for reversing the action or 'archive_wallets' for different resources. It lacks context about prerequisites, such as whether groups must be empty or active, and doesn't mention any exclusions or dependencies.

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