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

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`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
`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
`data_sources`	No	Where the numbers come from

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"
+    },
+    "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

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds useful behavioral context beyond those: the call is free, the list is maintained by a specific source, and 'new coins are added regularly', meaning the result set is not static. No contradiction with annotations.

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 short and front-loaded: cost first, then the action, then the source and mutability of the data. Every sentence contributes useful information and there is no filler.

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 listing tool with an output schema, the description covers cost, content, source, and the fact that new coins are added over time. It does not mention ordering or pagination, but the simplicity of the tool and presence of an output schema make these gaps minor.

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 has zero parameters, so there is no parameter documentation burden. The description still adds value by stating the output fields (symbol, name, category), which helps an agent understand the shape of the returned list.

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 states a specific verb ('Lists') and resource ('all cryptocurrencies currently evaluated by True Value Rankings') and enumerates returned fields: symbol, name, and category. This clearly distinguishes it from ranking- and value-specific siblings like get_top_ranked and get_tvr_score.

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?

It conveys when to use the tool: to get the full current inventory of evaluated coins. However, it does not explicitly contrast with sibling tools or state when a user should prefer get_top_ranked or get_full_breakdown instead. The usage context is implied by the plain 'lists all' framing rather than stated as guidance.

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.