Armor Crypto MCP

Official

Overview Schema Source Related Servers Discussions Admin

get_top_trending_tokens

Retrieve top trending tokens by market cap or volume for a selected time frame to compare token performance across minutes to 24 hours.

Instructions

Get the top trending tokens in a particular time frame. Great for comparing market cap or volume.

Expects a TopTrendingTokensRequest, returns a list of tokens with their details.

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": {
      "top_trending_tokens_requests": "<top_trending_tokens_requests>"
    },
    "name": "get_top_trending_tokens"
  }
}

Input Schema

Name	Required	Description	Default
`top_trending_tokens_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

B3.2/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions returning a list of tokens with details but does not explain what 'details' entail, nor does it disclose any read-only nature, rate limits, or potential costs.

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 with two sentences, the first stating the main action and the second adding technical context. It is front-loaded and efficient, though the second sentence is somewhat redundant given the schema.

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?

The description lacks explanation of what 'trending' means (e.g., based on price change, volume, or social signals) and how tokens are ranked. Despite having an output schema, the agent lacks context to fully understand the tool's purpose relative to siblings like get_token_candle_data.

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 coverage is 0% as the description does not elaborate on the parameters. Although the schema itself describes the time_frame parameter with an enum, the description adds no value beyond stating it expects a TopTrendingTokensRequest, failing to compensate for the low coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves top trending tokens for a given time frame and mentions it's useful for comparing market cap or volume, which distinguishes it from sibling tools like search_token_details or get_token_candle_data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for comparing market cap or volume over a time frame, but does not explicitly specify when to use this tool versus alternatives, nor does it provide when-not-to-use guidance.

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