True Value Rankings

List Evaluated Coins

list_coins

Read-onlyIdempotent

Free. Lists all cryptocurrencies currently evaluated by True Value Rankings with their symbol, name, and category. New coins are added regularly. 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)
`coins`	No	Covered coins with ticker and name
`error`	No	false on a normal answer, or an error message
`total`	No
`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
`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"
+    },
+    "coins": {
+      "description": "Covered coins with ticker and name",
+      "type": "array"
+    },
+    "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"
+    },
+    "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"
+    },
+    "total": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

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 readOnly, idempotent, non-destructive, and closed-world, so safety is covered. The description adds genuinely new behavior context: the call is free of charge and the coin set changes over time ('new coins are added regularly'), which warns the agent results are not a static catalog. No mention of list size or ordering, which is the only remaining gap.

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?

Three short sentences, front-loaded with the cost signal and the core action. Slight redundancy in naming 'True Value Rankings' twice (once as the evaluator, once as the data source), but nothing is misleading or padded.

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 zero-parameter read tool with a full output schema and rich annotations, the description covers what is returned (symbol, name, category), cost, and data freshness. Only freshness granularity and result ordering/size are left unstated, which is minor here.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly signals this is an unfiltered full listing rather than implying hidden filter options.

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?

Clear specific verb+resource: lists all cryptocurrencies evaluated by True Value Rankings, and names the returned fields (symbol, name, category). The word 'all' plus 'currently evaluated' separates it in spirit from ranked/filtered siblings like get_top_ranked and compare_coins, but it never names a sibling explicitly.

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?

No explicit when-to-use or when-not-to-use guidance. Usage is only implied: it is the natural discovery/entry-point call before get_tvr_score, compare_coins, or get_full_breakdown. The 'Free' prefix hints at cost considerations but does not state that other tools may be metered.

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.