True Value Rankings

Get TVR Score

get_tvr_score

Read-onlyIdempotent

Free. Returns the TVR Score, rank, valuation category, TVR Estimated Value, fair value gap, and all 8 metric scores for a cryptocurrency. Accepts a ticker (BTC) or a name (Bitcoin). TVR evaluates fundamental strength using Sound Value principles. Data from True Value Rankings (truevaluerankings.com). Rate limit: 100 requests per 15 minutes per IP.

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	All 8 metric scores with their weights
`fair_value_gap`	No	Gap between TVR Estimated Value and market price, formatted as a percentage
`weakest_metric`	No
`strongest_metric`	No
`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"
+    },
+    "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": {
+      "description": "All 8 metric scores with their weights"
+    },
+    "rank": {
+      "description": "Rank among evaluated coins, 1 is best",
+      "type": "number"
+    },
+    "rank_out_of": {
+      "description": "Number of coins evaluated",
+      "type": "number"
+    },
+    "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"
+    },
+    "strongest_metric": {},
+    "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"
+    },
+    "weakest_metric": {}
+  },
+  "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)"

First observedMar 16, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare the tool read-only, idempotent, and non-destructive. The description adds valuable behavioral context beyond that: it notes the tool is free, explicitly discloses a rate limit (100 requests per 15 minutes per IP), and cites the data source. This helps the agent anticipate throttling and provenance without contradicting any annotation.

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 at four sentences and covers essential information: cost, output, input format, methodology, data source, and rate limit. The first sentence quickly communicates 'Free' and the result set. Some minor redundancy exists (methodology sentence could be trimmed), but overall it is well-structured and not bloated.

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?

The tool has a single well-documented parameter, an output schema exists (so return values are structurally defined), and annotations cover safety semantics. The description completes the picture by naming the exact outputs, input flexibility, pricing, data provenance, and rate limit. An agent has everything needed to invoke this tool correctly.

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 parameter 'coin' is already well-described with examples. The description reinforces that the tool accepts a ticker or a name (e.g., BTC, Bitcoin), but adds no semantic meaning beyond what the schema already provides. A baseline of 3 is appropriate because the schema does the heavy lifting.

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 explicitly states the verb 'Returns' and enumerates the complete set of outputs (TVR Score, rank, valuation category, TVR Estimated Value, fair value gap, and all 8 metric scores). This clearly differentiates it from siblings like get_tvr_estimated_value by listing the full result set. An agent can immediately understand what this tool provides.

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

Usage Guidelines2/5

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

The description gives no explicit guidance on when to use this tool instead of its siblings. It does not name alternatives like get_full_breakdown or get_tvr_estimated_value, nor does it provide exclusion criteria. The only contextual hints are 'Free' and the rate limit, which do not help select between tools.

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.