True Value Rankings

Get Custom Ranking

get_custom_ranking

Read-only

Paid. Reranks every coin TVR covers with your own weights for the 8 fundamental metrics, applying TVR's non-public score transformation. Returns rank, TVR Score, valuation category, fair value gap and TVR Estimated Value per coin. $0.05 per call, paid in-band with x402 (USDC on Base) or MPP (USDC.e on Tempo); an unpaid call returns the offer (isError with the x402 PaymentRequired in structuredContent) and charges nothing. Invalid input is refused before any payment. Free alternative: get_top_ranked and the four presets. Data from True Value Rankings (truevaluerankings.com).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_custom_ranking"
  }
}

Input Schema

Name	Required	Description	Default
`coins`	No	Optional tickers or names (1-50). Omit for all covered coins.
`weights`	No	Up to 8 weights (0-100) in this order: economic_model, network_security, adoption, privacy, longevity, liquidity, legal_clarity, technical_dev, or an object keyed by those names. Missing entries take TVR defaults.

Output Schema

Name	Required	Description
`count`	No
`error`	No
`legal`	No
`reason`	No
`status`	No
`context`	No
`payment`	No
`product`	No
`success`	No
`rankings`	No	Ranked coins under the requested weights
`disclaimer`	No
`how_to_pay`	No
`learn_more`	No
`redelivery`	No
`weights_used`	No
`defaults_applied_for`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 17, 2026
RemovedSep 15, 2026
AddedMar 28, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations declare readOnlyHint=true and destructiveHint=false, and the description aligns, describing a non-mutating rerank. It adds valuable behavioral context beyond annotations: payment required, unpaid calls return an offer with isError, invalid input is refused before payment, and charges nothing on failure. This goes beyond the basic annotation profile.

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 well-structured, front-loading the critical 'Paid' flag and purpose, then covering payment details, error behavior, and alternatives. Every sentence earns its place, providing comprehensive information without redundancy.

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?

With an output schema present, return values are covered. The description explains the tool's scope, payment mechanics, error handling, and free alternatives. An agent has all necessary information to decide when to use this tool and how to invoke it correctly, including payment prerequisites.

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% with descriptions for both coins and weights. The description adds extra meaning by specifying that coins can be omitted for all covered coins and that weights follow a specific order with missing entries defaulting to TVR defaults, which is not fully in the schema. This enriches understanding beyond the schema.

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 clearly states the tool reranks all TVR-covered coins using custom weights for 8 metrics, applying a non-public score transformation. It distinguishes itself from siblings like get_top_ranked and presets, and mentions the paid nature, leaving no ambiguity about what it does.

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

Usage Guidelines5/5

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

Explicitly states 'Paid' and offers a 'Free alternative: get_top_ranked and the four presets,' giving agents a clear decision rule. It also details payment methods (x402/MPP) and the behavior on unpaid calls, ensuring correct invocation context.

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.