True Value Rankings

Get TVR Estimated Value

get_tvr_estimated_value

Read-onlyIdempotent

Free. Returns TVR's valuation category for a cryptocurrency (Undervalued, Fair Value or Overvalued) and the rule behind it. Label only: the exact TVR Estimated Value and Fair Value Gap, with the main reasons, come from get_fair_value_verdict ($0.02). Accepts a ticker or a name. 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": {
      "coin": "<coin>"
    },
    "name": "get_tvr_estimated_value"
  }
}

Input 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

Name	Required	Description
`coin`	No	Coin name
`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
`symbol`	No	Ticker
`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
`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
`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.
`fair_value_gap`	No	Gap between TVR Estimated Value and market price, formatted as a percentage
`valuation_rule`	No	The published valuation rule: Undervalued at least 4% above the market price, Overvalued more than 15% below it, Fair Value between
`tvr_estimated_value`	No	TVR Estimated Value, formatted in USD

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"
+    },
+    "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"
+    },
+    "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"
+    },
+    "symbol": {
+      "description": "Ticker",
+      "type": "string"
+    },
+    "tvr_estimated_value": {
+      "description": "TVR Estimated Value, formatted in USD",
+      "type": "string"
+    },
+    "valuation": {
+      "description": "Undervalued, Fair Value or Overvalued",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedSep 15, 2026

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 30, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive behavior, so the bar is lower. The description still adds useful context beyond that: cost is free, data provenance is truevaluerankings.com, and it discloses that the payload is a label, not the full valuation. It does not mention rate limits or caching, which keeps it from a 5.

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-loaded with the cost signal, then purpose, then routing to the paid sibling, then provenance — a sensible order with no wasted sentences. The only near-redundancy is the ticker-or-name sentence, which duplicates the input schema.

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?

An output schema exists, so return values need no explanation, and the description correctly confines itself to what the schema cannot convey: price, data source, and the boundary against get_fair_value_verdict. For a one-parameter read tool this is close to complete; only rate/usage limits are unaddressed.

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-or-name input with concrete examples (BTC, Bitcoin, ETH, XMR...). The description's 'Accepts a ticker or a name' merely repeats the schema, adding no new meaning. Baseline 3 is correct when the schema carries the load.

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: returns TVR's valuation category (Undervalued, Fair Value, Overvalued) plus the rule behind it for a cryptocurrency. It also explicitly delineates scope against the sibling get_fair_value_verdict by calling this 'label only', so an agent can distinguish the two without opening either schema.

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?

Names the alternative and the condition that selects it: if you need the exact TVR Estimated Value, Fair Value Gap, or reasons, use get_fair_value_verdict. Also signals cost ('Free' vs '$0.02'), which is a real selection factor here. It stops short of an explicit 'use this when you only need the label' instruction, but the routing is clear.

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.