True Value Rankings

Get Scoring Methodology

get_methodology

Read-onlyIdempotent

Free. Explains how True Value Rankings scores cryptocurrencies: the 8 metrics, their current default weights, the 4 built-in weight presets, and the general scoring approach. Data from True Value Rankings (truevaluerankings.com).

Input Schema

Name	Required	Description	Default
No arguments

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
`disclaimer`	No	Model-derived assessment, not investment advice
`learn_more`	No	Links for more detail
`attribution`	No	Required attribution text
`methodology`	No	The 8 metrics, their default weights and how the TVR Score is built
`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.
`valuation_rule`	No	The published valuation rule: Undervalued at least 4% above the market price, Overvalued more than 15% below it, Fair Value between

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"
+    },
+    "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"
+    },
+    "learn_more": {
+      "description": "Links for more detail"
+    },
+    "methodology": {
+      "description": "The 8 metrics, their default weights and how the TVR Score is built"
+    },
+    "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"
+    }
+  },
+  "type": "object"
+}

First observedMar 16, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds some useful context by saying the tool is free and names the data source, while noting that default weights and presets are covered, but it does not add details about rate limits, auth, or return behavior beyond what the output schema provides.

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?

The description is two sentences, front-loads the cost and core purpose, and lists the covered contents without redundant wording. Every sentence adds useful information.

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?

For a zero-parameter explanatory endpoint with rich annotations and an output schema, the description is complete: it states what the methodology covers, that weights and presets are included, and where the data comes from. No additional call details are needed.

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?

There are zero parameters, so the baseline is 4. The description appropriately does not discuss parameter semantics, and the empty schema is self-explanatory.

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 uses a specific verb, 'Explains,' and a specific resource, 'how True Value Rankings scores cryptocurrencies.' It also enumerates the scope: the 8 metrics, current default weights, 4 built-in presets, and general scoring approach, which distinguishes it from sibling tools that return scores or rankings.

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 the tool is for understanding the scoring methodology, but it does not explicitly state when to use it versus alternatives such as get_tvr_score, get_custom_ranking, or get_full_breakdown. No exclusions or prerequisites are given.

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.