Skip to main content
Glama

list_groups

Retrieve all wallet groups managed within the Armor Crypto MCP server to organize and access cryptocurrency holdings across multiple chains.

Instructions

List all wallet groups.

Returns a list of GroupInfo.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • MCP tool handler function for 'list_groups'. It checks authentication, calls the armor_client.list_groups() method, and returns the list of GroupInfo or an error.
    @mcp.tool()
    async def list_groups() -> List[GroupInfo]:
        """
        List all wallet groups.
        
        Returns a list of GroupInfo.
        """
        if not armor_client:
            return [{"error": "Not logged in"}]
        try:
            result: List[GroupInfo] = await armor_client.list_groups()
            return result
        except Exception as e:
            return [{"error": str(e)}]
  • Pydantic BaseModel defining the structure of GroupInfo, used as the return type for the list_groups tool.
    class GroupInfo(BaseModel):
        id: str = Field(description="id of the group")
        name: str = Field(description="name of the group")
        is_archived: bool = Field(description="whether the group is archived")
  • ArmorWalletAPIClient method that makes the actual GET API request to retrieve the list of wallet groups.
    async def list_groups(self) -> List[GroupInfo]:
        """Return a list of wallet groups."""
        return await self._api_call("GET", "wallets/groups/")
  • The @mcp.tool() decorator registers the list_groups function as an MCP tool.
    @mcp.tool()
Behavior2/5

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

With no annotations provided, the description carries full burden but only states it returns 'a list of GroupInfo' without detailing behavioral traits like pagination, rate limits, permissions, or error handling. This is insufficient for a 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise with two sentences that directly state the action and return value. There is no wasted language, and it is front-loaded with the core purpose.

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 tool's simplicity (0 parameters, output schema exists), the description is minimally adequate but lacks behavioral context. The output schema handles return values, but without annotations, more detail on operation traits would improve completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters with 100% schema description coverage, so the schema fully documents the absence of inputs. The description adds no parameter information, which is appropriate here, earning a baseline score above 3 due to the lack of parameters.

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 verb ('List') and resource ('all wallet groups'), making the purpose unambiguous. However, it doesn't distinguish itself from sibling tools like 'list_single_group' or 'create_groups', which would require explicit differentiation for a perfect score.

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 'list_single_group' or 'create_groups'. The description lacks context about prerequisites, timing, or exclusions, leaving usage decisions to inference.

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