True Value Rankings

Get TVR Estimated Value

get_tvr_estimated_value

Read-onlyIdempotent

Free. Returns TVR's fair value estimate (TVR Estimated Value) for a cryptocurrency, including the fair value gap and valuation category. The TVR Estimated Value compares fundamental quality to current market price. 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
`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
`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
`data_sources`	No	Where the numbers come from
`fair_value_gap`	No	Gap between TVR Estimated Value and market price, formatted as a percentage
`tvr_estimated_value`	No	TVR Estimated Value, formatted in USD

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"
+    },
+    "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.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds value beyond annotations by disclosing the data source ('Data from True Value Rankings'), that the tool is free, and what the estimate conceptually measures. No contradiction with annotations; the added source and cost context is genuinely helpful.

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?

Four sentences with zero waste: cost, return contents, conceptual meaning, input format, and data source are each covered once. The most important information (what it returns) is front-loaded, and every sentence earns its place. No redundancy with annotations or 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?

For a single-parameter lookup tool with an output schema present and annotations covering the safety profile, the description is nearly complete. It covers cost, source, input format, and the meaning of the value. The only minor gap is the absence of alternative-routing guidance, which is covered under usage_guidelines rather than completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with a well-described 'coin' parameter including examples. The description adds meaning beyond the schema by explicitly stating the accepted input forms ('Accepts a ticker or a name'), clarifying that either format works, which the schema only implies through examples. This is a useful addition, though modest given the schema's strength.

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 names a specific verb ('Returns'), the specific resource (TVR's fair value estimate), and the exact contents (fair value gap, valuation category). It is clearly distinguishable from sibling tools like get_tvr_score and get_top_ranked by focusing on 'Estimated Value' for a single coin. The phrase 'compares fundamental quality to current market price' further clarifies the semantics.

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 (a lookup tool for a single cryptocurrency's fair value estimate) and confirms input format ('Accepts a ticker or a name'), but it never names alternatives or states when NOT to use it versus get_tvr_score or get_full_breakdown. No explicit routing or exclusion guidance is provided, leaving the agent to infer context from the tool name and siblings.

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.