Armor Crypto MCP

Official

by armorwallet

Overview Schema Source Related Servers Discussions Admin

Python

Remote

get_token_candle_data

Fetch candlestick data for any token by specifying a time range and interval for price or market cap analysis.

Instructions

Get candle data about any token for analysis.

Expects a CandleStickRequest, returns a list of candle sticks.

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": {
      "candle_stick_requests": "<candle_stick_requests>"
    },
    "name": "get_token_candle_data"
  }
}

Input Schema

Name	Required	Description	Default
`candle_stick_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.9/5.0

Behavior2/5

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

No annotations are provided, and the description only states input/output types. It does not disclose behavioral traits such as data limits, pagination, or permission requirements, which are critical for a data retrieval tool.

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 short (2 sentences) with no wasted words. The first sentence states purpose, the second clarifies input/output. However, it could be more informative within the same length.

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 complexity of the nested CandleStickRequest object and the lack of annotations, the description is insufficient. It doesn't explain the token address requirement, time formats, or how to handle large datasets, leaving significant gaps for an agent.

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 descriptions cover all parameters (100%), so baseline is 3. The tool description adds nothing beyond the schema, providing no additional context or validation hints.

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 'Get candle data about any token for analysis', which is a specific verb+resource. It distinguishes this tool from siblings by focusing on candle data, though it doesn't explicitly differentiate from other data retrieval tools.

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 on when to use this tool versus alternatives like search_token_details or get_wallet_token_balance. The description lacks context for appropriate usage scenarios.

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