Skip to main content
Glama

create_groups

Organize cryptocurrency wallets into named groups for better management and categorization within the Armor Crypto MCP server.

Instructions

Create new wallet groups.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
create_groups_requestsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • MCP tool handler for 'create_groups': decorated with @mcp.tool(), validates input, calls armor_client.create_groups(), handles errors and returns List[CreateGroupResponse] or error.
    @mcp.tool()
    async def create_groups(create_groups_requests: CreateGroupsRequestContainer) -> List[CreateGroupResponse]:
        """
        Create new wallet groups.
        
        Expects a list of group names, returns a list of CreateGroupResponse.
        """
        if not armor_client:
            return [{"error": "Not logged in"}]
        try:
            result: List[CreateGroupResponse] = await armor_client.create_groups(create_groups_requests)
            return result
        except Exception as e:
            return [{"error": str(e)}]
  • Pydantic input schema container for create_groups tool: holds list of CreateGroupsRequest objects.
    class CreateGroupsRequestContainer(BaseModel):
        create_groups_requests: List[CreateGroupsRequest]    
  • Pydantic schema for individual group creation request: contains the group 'name'.
    class CreateGroupsRequest(BaseModel):
        name: str = Field(description="Name of the group to create")
  • Pydantic output schema for created group: includes id, name, is_archived.
    class CreateGroupResponse(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")
  • Helper method in ArmorWalletAPIClient that prepares payload from container and makes POST API call to /wallets/groups/ to create groups.
    async def create_groups(self, data: CreateGroupsRequest) -> List[CreateGroupResponse]:
        """Create new wallet groups given a list of group names."""
        # payload = json.dumps([{"name": group_name} for group_name in data.group_names])
        payload = data.model_dump(exclude_none=True)['create_groups_requests']
        return await self._api_call("POST", "wallets/groups/", payload)
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 the input format ('list of group names') and output format ('list of CreateGroupResponse'), but lacks critical details: required permissions, whether groups can be modified/deleted later, rate limits, or error handling. For a creation tool with zero annotation coverage, this is insufficient.

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 only two sentences that are front-loaded and waste-free. The first sentence states the purpose, and the second covers input/output expectations efficiently.

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 complexity (creation operation), lack of annotations, and 0% schema coverage, the description is incomplete. However, the presence of an output schema mitigates the need to describe return values in the description. Still, critical behavioral and parameter details are missing for a mutation tool.

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%, so the description must compensate. It mentions 'list of group names' which hints at the parameter's purpose, but doesn't explain the actual parameter name 'create_groups_requests', its structure, or constraints (e.g., name format, duplicates). The description adds minimal value beyond the bare schema.

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 'Create' and the resource 'new wallet groups', which is specific and unambiguous. It distinguishes from siblings like 'list_groups' (read) and 'archive_wallet_group' (modify), though it doesn't explicitly differentiate from 'create_wallet' (which creates 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. It doesn't mention prerequisites (e.g., needing existing wallets first), compare to 'create_wallet' for individual wallets, or specify when group creation is appropriate versus other operations like adding wallets to groups.

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