Skip to main content
Glama

Token Command Center

tc_compare

Read-only

Two to six tokens side by side: price, valuation, revenue and its 7/30-day change, revenue_figures per token (30-day annualized pace and real last-12-months revenue, P/S on both), holders revenue, net-flow yield, P/S, unlocks, health with six pillar scores, verdict, lens, and any frozen-price or old-scorecard flags. Accepts slugs or unambiguous symbols.

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": {
      "tokens": "<tokens>"
    },
    "name": "tc_compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNo
tokensYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / fields / items / enum
      Previous value: -[
      -  "alerts",
      -  "arr",
      -  "arr_30d",
      -  "arr_7d",
      -  "category",
      -  "conflicts",
      -  "date",
      -  "fdv",
      -  "flow_model",
      -  "health",
      -  "health_change",
      -  "holders_rev",
      -  "lens",
      -  "mcap",
      -  "name",
      -  "net_flow",
      -  "nf_yield",
      -  "pct_unlocked",
      -  "price",
      -  "price_frozen_days",
      -  "ps",
      -  "scorecard_age_days",
      -  "stale",
      -  "symbol",
      -  "tier",
      -  "unlock_30d",
      -  "verdict"
      -]New value: +[
      +  "alerts",
      +  "arr",
      +  "arr_30d",
      +  "arr_7d",
      +  "category",
      +  "conflicts",
      +  "date",
      +  "fdv",
      +  "flow_model",
      +  "health",
      +  "health_change",
      +  "holders_rev",
      +  "lens",
      +  "mcap",
      +  "name",
      +  "net_flow",
      +  "nf_yield",
      +  "pct_unlocked",
      +  "price",
      +  "price_frozen_days",
      +  "ps",
      +  "scorecard_age_days",
      +  "sector",
      +  "stale",
      +  "symbol",
      +  "tier",
      +  "unlock_30d",
      +  "verdict"
      +]
  2. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds real substance on top by enumerating the returned dimensions and flagging special states (frozen price, old scorecard, stale, conflicts). It does not mention rate limits, payload size for six tokens, or how missing data is represented.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single dense sentence front-loads the scope correctly, but the metric enumeration is a long laundry list that partly restates the `fields` enum and buries the one operational note (slug/symbol acceptance) at the end. It is informative rather than padded, but structure could be tighter.

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?

With no output schema, the description does the heavy lifting on return values and does it well, which is the main completeness risk here. However, for a two-parameter tool it omits the `fields` projection entirely, so an agent cannot tell it may request a subset of the 30 available fields.

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%, so the description must carry both parameters. It explains `tokens` (slugs or unambiguous symbols) but never mentions the `fields` parameter at all, leaving an 18-item enum-constrained projection undocumented in both schema and prose. It also says "two to six" while the schema permits minItems=1, a minor inconsistency an agent could trip on.

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?

"Two to six tokens side by side" states the resource and the comparison scope precisely, and the metric list makes clear this is a multi-token comparison rather than a single-token lookup. It never names a sibling (e.g. tc_get_token or tc_screen) to contrast against, so differentiation is implied by scope rather than stated.

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?

Usage is implied by the comparison framing and the input note "accepts slugs or unambiguous symbols," which hints that ambiguous symbols need resolving first. There is no explicit when-to-use versus tc_get_token/tc_screen guidance and no statement of what happens at the boundaries (fewer than two tokens, more than six).

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.

Resources