Armor Crypto MCP

Official

Overview Schema Source Related Servers Discussions Admin

calculate_token_conversion

Calculate token conversion quotes between two tokens. Provide input token address, amount, and output token address to receive conversion responses with market prices.

Instructions

Perform token conversion quote between two tokens. Good for quickly calculating market prices.

Expects a ConversionRequestContainer, returns a list of ConversionResponse.

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": {
      "conversion_requests": "<conversion_requests>"
    },
    "name": "calculate_token_conversion"
  }
}

Input Schema

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

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 only mentions input and output types but does not disclose behavioral traits such as idempotency, error handling, or rate limits.

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?

Three sentences efficiently convey the action, usage context, and input/output types without unnecessary words.

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?

The description is basic and lacks guidance against similar tools like swap_quote. It mentions output type but does not cover error scenarios or additional behavioral context.

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 for the top-level parameter is 0%. The description adds only that it expects a ConversionRequestContainer, which is already in the schema. It does not add meaning beyond the schema for the parameters.

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 performs a token conversion quote between two tokens. It provides a specific verb and resource, but does not differentiate from similar sibling tools like swap_quote.

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 phrase 'Good for quickly calculating market prices' implies usage context, but there is no explicit guidance on when to use this tool versus alternatives like swap_quote or when not to use it.

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