True Value Rankings

Compare Coins

compare_coins

Read-onlyIdempotent

Free. Compares 2 to 5 cryptocurrencies on TVR Score, rank, valuation category and all 8 metric scores side by side, and identifies the largest scoring difference. Exact Fair Value Gaps and TVR Estimated Values are in get_fair_value_verdict ($0.02 per coin). Accepts tickers or names. Data from True Value Rankings (truevaluerankings.com).

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": {
      "coins": "<coins>"
    },
    "name": "compare_coins"
  }
}

Input Schema

Name	Required	Description	Default
`coins`	Yes	Array of 2-5 cryptocurrency tickers or names to compare (e.g., ["BTC", "Ethereum", "SOL"])

Output Schema

Name	Required	Description
`as_of`	No	When the prices behind this answer were taken (prices_as_of) and the day the coin's eight metric scores last changed (scores_last_changed)
`error`	No	false on a normal answer, or an error message
`status`	No	Present when the request could not be answered as asked, for example not_available
`context`	No	Standing context about TVR and how to read its outputs
`summary`	No	Plain-language summary of the answer
`trimmed`	No	Present when this free answer leaves out the exact figures and written reasons, with where to find them
`requested`	No	What was asked for, when it could not be resolved
`comparison`	No	Per-coin scores, ranks and valuations
`disclaimer`	No	Model-derived assessment, not investment advice
`learn_more`	No	Links for more detail
`attribution`	No	Required attribution text
`paid_option`	No	Where relevant: the paid TVR capability that goes further than this free answer, with its price, how to pay, the licence and an example call. Nothing is charged unless the client pays.
`data_sources`	No	Where the numbers come from
`paid_verdict`	No	The paid fair value verdict for a coin: the exact Fair Value Gap and TVR Estimated Value with the main reasons and caveats, its price and how to call it. Nothing is charged unless the client pays.
`coins_compared`	No
`key_difference`	No	The largest gap between the compared coins
`valuation_rule`	No	The published valuation rule: Undervalued at least 4% above the market price, Overvalued more than 15% below it, Fair Value between
`metric_comparison`	No	Metric-by-metric table
`total_coins_evaluated`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 5, 2026

addedOutput schema / properties / as_of

Added value: +{
+  "description": "When the prices behind this answer were taken (prices_as_of) and the day the coin's eight metric scores last changed (scores_last_changed)"
+}

addedOutput schema / properties / paid_verdict

Added value: +{
+  "description": "The paid fair value verdict for a coin: the exact Fair Value Gap and TVR Estimated Value with the main reasons and caveats, its price and how to call it. Nothing is charged unless the client pays."
+}

addedOutput schema / properties / trimmed

Added value: +{
+  "description": "Present when this free answer leaves out the exact figures and written reasons, with where to find them"
+}

addedOutput schema / properties / valuation_rule

Added value: +{
+  "description": "The published valuation rule: Undervalued at least 4% above the market price, Overvalued more than 15% below it, Fair Value between",
+  "type": "string"
+}

Changed1 schema field changedOct 31, 2026

addedOutput schema / properties / paid_option

Added value: +{
+  "description": "Where relevant: the paid TVR capability that goes further than this free answer, with its price, how to pay, the licence and an example call. Nothing is charged unless the client pays."
+}

Changed1 schema field changedSep 16, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "attribution": {
+      "description": "Required attribution text",
+      "type": "string"
+    },
+    "coins_compared": {
+      "type": "number"
+    },
+    "comparison": {
+      "description": "Per-coin scores, ranks and valuations"
+    },
+    "context": {
+      "description": "Standing context about TVR and how to read its outputs"
+    },
+    "data_sources": {
+      "description": "Where the numbers come from"
+    },
+    "disclaimer": {
+      "description": "Model-derived assessment, not investment advice",
+      "type": "string"
+    },
+    "error": {
+      "description": "false on a normal answer, or an error message"
+    },
+    "key_difference": {
+      "description": "The largest gap between the compared coins"
+    },
+    "learn_more": {
+      "description": "Links for more detail"
+    },
+    "metric_comparison": {
+      "description": "Metric-by-metric table"
+    },
+    "requested": {
+      "description": "What was asked for, when it could not be resolved",
+      "type": "string"
+    },
+    "status": {
+      "description": "Present when the request could not be answered as asked, for example not_available",
+      "type": "string"
+    },
+    "summary": {
+      "description": "Plain-language summary of the answer",
+      "type": "string"
+    },
+    "total_coins_evaluated": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedSep 15, 2026

changedInput schema / properties / coins / description

Previous value: -"Array of 2-5 cryptocurrency ticker symbols to compare (e.g., [\"BTC\", \"ETH\", \"SOL\"])"New value: +"Array of 2-5 cryptocurrency tickers or names to compare (e.g., [\"BTC\", \"Ethereum\", \"SOL\"])"

First observedMar 16, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: the tool is free, the comparison is capped at 2–5 coins, and it surfaces the largest scoring difference as an analytical output, with data sourced from truevaluerankings.com.

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?

Front-loads the decisive fact ("Free.") and packs scope, output content, and the paid alternative into three tight sentences. The source attribution to truevaluerankings.com is marginally expendable but harmless.

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

Completeness5/5

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

An output schema exists, so return values need not be described, and the description still names the compared dimensions. Cost, input constraints, accepted input forms, and the paid alternative are all present — nothing an agent needs to invoke this correctly is missing.

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%, and the schema already documents the 2–5 item bounds and ticker-or-name examples. The description's "Accepts tickers or names" restates what the schema says rather than adding format or normalization rules, so this sits at the baseline.

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?

States a specific verb and resource ("Compares 2 to 5 cryptocurrencies") and enumerates exactly what is compared: TVR Score, rank, valuation category, and all 8 metric scores side by side, plus the largest scoring difference. This is clearly separable from siblings like get_tvr_score or get_full_breakdown, which operate on one coin.

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

Usage Guidelines4/5

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

Explicitly routes the agent to get_fair_value_verdict when exact Fair Value Gaps and TVR Estimated Values are needed, and discloses that this alternative costs $0.02 per coin — a strong when-to-use signal. It stops short of covering other plausible siblings such as get_full_breakdown or get_top_ranked, so the routing map is incomplete.

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

All True Value Rankings tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.