Skip to main content
Glama

token_compare

Read-onlyIdempotent

Compare a primary token against up to 3 others. Returns full research on primary, abbreviated metrics on comparisons, plus AI comparative analysis. Free over MCP for 10 calls per day; beyond that the tool returns the pay-per-call x402 endpoint and its price.

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": {
      "primary": "<primary>",
      "compare": "<compare>"
    },
    "name": "token_compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoBlockchain networkethereum
compareYesTokens to compare against (1-3)
primaryYesPrimary token to research

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare read-only, idempotent, open-world, and non-destructive behavior. The description adds meaningful context beyond the annotations: it discloses the response composition and the free 10-call-per-day MCP quota, after which a paid x402 endpoint is returned.

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 three tightly written sentences with no wasted wording. It front-loads the core comparison purpose and then adds return behavior and quota details in a logical order.

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

Completeness4/5

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

For a tool without an output schema, the description provides useful return-value context: full research on the primary token, abbreviated comparison metrics, and AI analysis. It also documents the paywall behavior, though it does not specify token identifier format or error handling.

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?

Schema description coverage is 100%, so the input schema already documents primary, compare, and chain. The description reinforces that compare takes up to three tokens, but it does not add significant meaning beyond the schema, especially for the chain parameter.

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 states a specific verb and resource: comparing a primary token against up to three others. It also clarifies the scope of returned research, making it distinguishable from single-token research tools such as token_research.

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 when to use the tool by describing a comparison scenario and its return shape. However, it does not explicitly state when not to use it or name alternative sibling tools for single-token research versus comparison.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.