Skip to main content
Glama
armorwallet
by armorwallet

list_single_group

Retrieve detailed information for a specific wallet group by providing its name. This tool enables users to access SingleGroupInfo for efficient blockchain operations within the Armor Crypto MCP environment.

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 for 'list_single_group'. Registered via @mcp.tool() decorator. Delegates to armor_client.list_single_group and handles errors.
    @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)}
  • Registration of the 'list_single_group' tool using FastMCP @mcp.tool() decorator. Tool name derived from function name.
    @mcp.tool()
  • Pydantic input schema/model for the list_single_group tool: expects group_name.
    class ListSingleGroupRequest(BaseModel):
        group_name: str = Field(description="Name of the group to retrieve details for")
  • ArmorWalletAPIClient helper method implementing the API call to retrieve 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}/")
  • Pydantic output schema/model for SingleGroupInfo returned by list_single_group.
    class SingleGroupInfo(GroupInfo):
        wallets: List[WalletInfo] = Field(description="list of wallets in the group")
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the tool retrieves details (implying a read-only operation) and mentions the return type ('SingleGroupInfo'), but fails to disclose critical behavioral traits like error handling (e.g., what happens if the group doesn't exist), authentication needs, rate limits, or whether it's idempotent. This leaves significant gaps for an agent.

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: the first sentence states the purpose, and the second adds parameter and return details. Both sentences earn their place, with no wasted words. However, the structure could be slightly improved by integrating parameter guidance more seamlessly.

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 low complexity (1 parameter) and the presence of an output schema (which handles return values), the description is somewhat complete. It covers the basic purpose and parameter, but lacks behavioral details (e.g., error cases) and usage guidelines, making it adequate but with clear gaps for an agent to operate effectively.

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 input schema has 0% description coverage, but the description adds minimal value: it mentions 'group name' as the parameter and that it's required. However, it doesn't explain the parameter's semantics beyond what's inferred from the name (e.g., format, constraints, or examples). With low schema coverage, this is inadequate compensation, but it meets the baseline for having some param info.

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 tool's purpose: 'Retrieve details for a single wallet group.' It specifies the verb ('retrieve') and resource ('single wallet group'), distinguishing it from siblings like 'list_groups' (which presumably lists multiple groups). However, it doesn't explicitly contrast with 'list_groups' or other retrieval tools, preventing 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?

The description provides minimal guidance: it mentions the required parameter ('group name') and implies usage when details for a specific group are needed. However, it lacks explicit when-to-use instructions, such as when to choose this over 'list_groups' or other sibling tools, and offers no prerequisites or exclusions.

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