True Value Rankings

Get Full Breakdown

get_full_breakdown

Read-onlyIdempotent

Free. Returns the complete fundamental analysis for a cryptocurrency: all 8 metric scores with weights, the scoring factors that shaped them, the valuation note, and ranking context. Accepts a ticker or a name. Data from True Value Rankings (truevaluerankings.com).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`coin`	Yes	Cryptocurrency ticker or name (e.g., BTC, Bitcoin, ETH, LTC, XMR, SOL, ADA, AVAX, DOT, POL, LINK)

Output Schema

TableJSON Schema

Name	Required	Description
`coin`	No	Coin name
`rank`	No	Rank among evaluated coins, 1 is best
`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
`symbol`	No	Ticker
`context`	No	Standing context about TVR and how to read its outputs
`summary`	No	Plain-language summary of the answer
`category`	No	TVR coin category
`requested`	No	What was asked for, when it could not be resolved
`tvr_score`	No	TVR Score, 0 to 100
`valuation`	No	Undervalued, Fair Value or Overvalued
`disclaimer`	No	Model-derived assessment, not investment advice
`learn_more`	No	Links for more detail
`attribution`	No	Required attribution text
`rank_out_of`	No	Number of coins evaluated
`data_sources`	No	Where the numbers come from
`metric_scores`	No
`fair_value_gap`	No	Gap between TVR Estimated Value and market price, formatted as a percentage
`valuation_note`	No
`ranking_context`	No
`scoring_factors`	No	The reasoning behind each metric score
`tvr_estimated_value`	No	TVR Estimated Value, formatted in USD
`scoring_methodology_note`	No

Schema Changelog

Changes observed during successful MCP inspections.

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"
+    },
+    "category": {
+      "description": "TVR coin category",
+      "type": "string"
+    },
+    "coin": {
+      "description": "Coin name",
+      "type": "string"
+    },
+    "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"
+    },
+    "fair_value_gap": {
+      "description": "Gap between TVR Estimated Value and market price, formatted as a percentage",
+      "type": "string"
+    },
+    "learn_more": {
+      "description": "Links for more detail"
+    },
+    "metric_scores": {},
+    "rank": {
+      "description": "Rank among evaluated coins, 1 is best",
+      "type": "number"
+    },
+    "rank_out_of": {
+      "description": "Number of coins evaluated",
+      "type": "number"
+    },
+    "ranking_context": {},
+    "requested": {
+      "description": "What was asked for, when it could not be resolved",
+      "type": "string"
+    },
+    "scoring_factors": {
+      "description": "The reasoning behind each metric score"
+    },
+    "scoring_methodology_note": {
+      "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"
+    },
+    "symbol": {
+      "description": "Ticker",
+      "type": "string"
+    },
+    "tvr_estimated_value": {
+      "description": "TVR Estimated Value, formatted in USD",
+      "type": "string"
+    },
+    "tvr_score": {
+      "description": "TVR Score, 0 to 100",
+      "type": "number"
+    },
+    "valuation": {
+      "description": "Undervalued, Fair Value or Overvalued",
+      "type": "string"
+    },
+    "valuation_note": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed2 schema fields changedSep 15, 2026

removedInput schema / properties / _meta

Removed value: -{
-  "description": "Payment metadata (handled automatically by MPP-enabled clients)"
-}

changedInput schema / properties / coin / description

Previous value: -"Cryptocurrency ticker symbol (e.g., BTC, ETH, LTC, XMR, SOL, ADA, AVAX, DOT, POL, LINK)"New value: +"Cryptocurrency ticker or name (e.g., BTC, Bitcoin, ETH, LTC, XMR, SOL, ADA, AVAX, DOT, POL, LINK)"

AddedMar 28, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior, so the safety profile is covered. The description adds useful context: it is free, data comes from truevaluerankings.com, and the output includes metric scores, weights, factors, valuation note, and ranking context. It does not describe edge cases or response ordering, but with annotations present this is adequate.

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 compact and front-loads the key return-value information. The initial 'Free.' is slightly extraneous but not harmful; the rest is dense and useful.

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?

With one well-documented parameter, an output schema, and annotations covering safety, the description adds enough context about the response contents. It doesn't explain how to interpret the ranking context or what happens with invalid tickers, but those are not required for selecting and invoking the tool correctly given the output schema.

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 coverage is 100% and the single 'coin' parameter already documents ticker/name with examples. The description repeats 'Accepts a ticker or a name' without adding format, normalization, or case-sensitivity details, so it stays at the high-coverage baseline.

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 uses the specific verb 'Returns' with a clear resource: the complete fundamental analysis for a cryptocurrency, enumerating all 8 metric scores with weights, scoring factors, valuation note, and ranking context. This differentiates it from siblings like get_tvr_score, though it does not explicitly name an alternative.

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 when a full fundamental breakdown is needed, and 'Accepts a ticker or a name' clarifies input flexibility. However, it offers no explicit when-to-use vs alternatives such as compare_coins or get_tvr_score, nor any exclusions.

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.