Skip to main content
Glama
Sign In

True Value Rankings

by com.truevaluerankings
OverviewDiscussionsAdmin

Get Top Ranked Coins

get_top_ranked
Read-onlyIdempotent

Free. Returns the top N cryptocurrencies by a chosen ranking method: tvr_score (fundamental strength), most_undervalued (largest positive fair value gap first) or most_overvalued (largest negative fair value gap first), with each coin's TVR Score and valuation category. Exact gaps and TVR Estimated Values are in get_fair_value_verdict ($0.02 per coin). Data from True Value Rankings (truevaluerankings.com).

Input Schema

NameRequiredDescriptionDefault
countNoNumber of coins to return (default 5)
rank_byNoRanking method: tvr_score, most_undervalued, or most_overvaluedtvr_score

Output Schema

NameRequiredDescriptionDefault
as_ofNoWhen the prices behind this answer were taken (prices_as_of) and the day the coin's eight metric scores last changed (scores_last_changed)
errorNofalse on a normal answer, or an error message
statusNoPresent when the request could not be answered as asked, for example not_available
contextNoStanding context about TVR and how to read its outputs
rank_byNoThe ranking basis used
summaryNoPlain-language summary of the answer
trimmedNoPresent when this free answer leaves out the exact figures and written reasons, with where to find them
rankingsNoOrdered list of coins
requestedNoWhat was asked for, when it could not be resolved
disclaimerNoModel-derived assessment, not investment advice
learn_moreNoLinks for more detail
attributionNoRequired attribution text
paid_optionNoWhere 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_sourcesNoWhere the numbers come from
paid_verdictNoThe 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_ruleNoThe published valuation rule: Undervalued at least 4% above the market price, Overvalued more than 15% below it, Fair Value between
rank_by_descriptionNo
total_coins_evaluatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • 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"
+}
  2. Changed1 schema field changed
    • 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."
+}
  3. Changed1 schema field changed
    • 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"
+    },
+    "rank_by": {
+      "description": "The ranking basis used",
+      "type": "string"
+    },
+    "rank_by_description": {
+      "type": "string"
+    },
+    "rankings": {
+      "description": "Ordered list of coins",
+      "type": "array"
+    },
+    "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_coins_evaluated": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}
  4. Changed2 schema fields changed
    • changedInput schema / properties / count / description
      Previous value: -"Number of coins to return (1-10, default 5)"New value: +"Number of coins to return (default 5)"
    • changedInput schema / properties / count / maximum
      Previous value: -10New value: +50
  5. Changed2 schema fields changed
    • changedInput schema / properties / count / description
      Previous value: -"Number of top-ranked coins to return (1-10, default 5)"New value: +"Number of coins to return (1-10, default 5)"
    • addedInput schema / properties / rank_by
      Added value: +{
+  "default": "tvr_score",
+  "description": "Ranking method: tvr_score, most_undervalued, or most_overvalued",
+  "enum": [
+    "tvr_score",
+    "most_undervalued",
+    "most_overvalued"
+  ],
+  "type": "string"
+}
  6. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely non-schema information: the tool is free, the paid boundary sits at get_fair_value_verdict, and results include the TVR Score plus a valuation category but omit exact gaps and estimated values — that tells an agent what it will NOT get back. Pagination and result-format details are left to the output schema.

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?

Front-loads the two things an agent needs to gate on first — cost ("Free") and the ranked-list purpose — then compresses the three ranking modes into one sentence. It is dense but every clause carries information; the only mild cost is a long run-on middle sentence rather than scannable structure.

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 two-parameter read tool with an output schema and full annotations, this covers everything: cost, ranking semantics, what fields are returned, what is deliberately withheld, and the sibling that supplies the withheld data. Nothing needed to invoke it correctly is missing.

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%, so the baseline is 3, but the description earns an upgrade by defining what each rank_by enum value actually sorts on (fundamental strength vs. positive vs. negative fair value gap direction). That is real semantic meaning beyond the schema's bare enum listing. The count parameter is fully handled by the schema and gets no extra treatment here.

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?

Names a specific verb and resource ("Returns the top N cryptocurrencies") and immediately disambiguates the three ranking modes: tvr_score = fundamental strength, most_undervalued = largest positive fair value gap first, most_overvalued = largest negative gap first. An agent can distinguish this from sibling tools like list_coins or get_custom_ranking without opening any schema.

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

Usage Guidelines4/5

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

Gives clear context: this is the free tier for ranked lists, and it explicitly routes the agent to get_fair_value_verdict when exact gaps or TVR Estimated Values are needed, including the cost ($0.02 per coin). It does not name exclusions against get_tvr_score (single coin) or list_coins, so the when-not-to-use side is only partially covered.

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 toolsInspect
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.

Resources