Armor Crypto MCP

Official

by armorwallet

Overview Schema Source Related Servers Discussions Admin

Python

Remote

get_all_wallets

Retrieve all wallets and their asset balances. Optionally include archived wallets.

Instructions

Retrieve all wallets with balances.

Returns a list of Wallets and asssets

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "get_all_wallets_requests": "<get_all_wallets_requests>"
    },
    "name": "get_all_wallets"
  }
}

Input Schema

Name	Required	Description	Default
`get_all_wallets_requests`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 18, 2025

TDQS

C2.7/5.0

Behavior2/5

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It states that the tool returns a list but omits important details such as whether the operation is read-only, the effect of the 'is_archived' parameter, authentication requirements, or any rate limits. The description is insufficient to set accurate agent expectations.

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 short (two sentences) and front-loads the purpose. However, it contains a typo ('asssets') and the second sentence is incomplete ('Returns a list of Wallets and asssets'). The conciseness is good, but the structure could be improved by correcting the typo and integrating the parameter information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the existence of an output schema, the description does not need to detail return fields, but it fails to provide essential context such as the scope of wallets (all user wallets?), default filtering behavior (archived excluded), or how to paginate. The tool has one parameter and an output schema, yet the description is too sparse to enable confident use.

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 tool description does not explain the parameter. Although the input schema itself describes the 'is_archived' property, the description fails to mention it, so the agent must infer its existence from the schema. The description adds no value beyond the schema for 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 uses a clear verb ('Retrieve') and resource ('all wallets'), and specifies that it returns balances. It effectively distinguishes this tool from siblings like 'get_wallet_token_balance' which targets a single wallet. However, it could be more explicit about the scope (e.g., user's wallets).

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, nor does it mention any prerequisites, exclusions, or context where other tools would be more appropriate. For example, it does not clarify that archived wallets are excluded by default or when 'get_wallet_token_balance' might be preferred.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.