Skip to main content
Glama

list_single_group

Retrieve details for a specific wallet group by providing the group name, enabling management of cryptocurrency assets within the Armor Crypto MCP server.

Instructions

Retrieve details for a single wallet group.

Expects the group name as a parameter, returns SingleGroupInfo.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
list_single_group_requestsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesid of the group
nameYesname of the group
walletsYeslist of wallets in the group
is_archivedYeswhether the group is archived

Implementation Reference

  • MCP tool handler function for 'list_single_group', decorated with @mcp.tool() for registration, which proxies to armor_client.list_single_group
    @mcp.tool()
    async def list_single_group(list_single_group_requests: ListSingleGroupRequest) -> SingleGroupInfo:
        """
        Retrieve details for a single wallet group.
        
        Expects the group name as a parameter, returns SingleGroupInfo.
        """
        if not armor_client:
            return {"error": "Not logged in"}
        try:
            result: SingleGroupInfo = await armor_client.list_single_group(list_single_group_requests)
            return result
        except Exception as e:
            return {"error": str(e)}
  • Pydantic input schema model ListSingleGroupRequest defining the group_name parameter
    class ListSingleGroupRequest(BaseModel):
        group_name: str = Field(description="Name of the group to retrieve details for")
  • ArmorWalletAPIClient helper method implementing the API call to fetch single group details
    async def list_single_group(self, data: ListSingleGroupRequest) -> SingleGroupInfo:
        """Return details for a single wallet group."""
        return await self._api_call("GET", f"wallets/groups/{data.group_name}/")
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 states the tool retrieves details (implying a read-only operation) and mentions the return type ('SingleGroupInfo'), but lacks critical information such as error handling (e.g., what happens if the group doesn't exist), authentication requirements, rate limits, or data freshness. For a read tool with zero annotation coverage, this is insufficient to inform the agent fully about its behavior.

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 concise and front-loaded, with two sentences that directly state the purpose and key details (parameter and return type). There's no unnecessary information or redundancy. However, the brevity comes at the cost of completeness, as noted in other dimensions, but within its limited scope, it's efficiently structured.

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 moderate complexity (single parameter, read operation) and the presence of an output schema (which handles return values), the description is minimally adequate. It covers the basic purpose and parameter hint but lacks details on usage guidelines, behavioral traits, and parameter specifics. With no annotations and low schema coverage, it doesn't fully compensate for these gaps, making it incomplete for reliable agent 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 input schema provides no descriptions for its single parameter. The description adds some value by specifying that the parameter is 'group name', but it doesn't explain the parameter's format, constraints, or how it relates to the nested 'ListSingleGroupRequest' structure. This leaves significant gaps in understanding the parameter's semantics, failing to compensate for the low schema coverage.

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 ('Retrieve details') and resource ('for a single wallet group'), making the purpose specific and understandable. It distinguishes from siblings like 'list_groups' by focusing on a single group rather than listing multiple groups. However, it doesn't explicitly contrast with other retrieval tools like 'get_wallet_token_balance' or 'get_all_wallets', which slightly limits differentiation.

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 minimal guidance: it mentions the required parameter ('group name') but offers no context on when to use this tool versus alternatives. There's no mention of prerequisites (e.g., group existence), exclusions, or comparisons to siblings like 'list_groups' for multiple groups or 'get_wallet_token_balance' for wallet-specific data. This leaves the agent with little direction on appropriate 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