Skip to main content
Glama

get_tvr_estimated_value

Returns TVR's fair value estimate (TVR Price) for a cryptocurrency, including the fair value gap and valuation category. TVR Price compares fundamental quality to current market price. Data from True Value Rankings (truevaluerankings.com).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
coinYesCryptocurrency ticker symbol (e.g., BTC, ETH, LTC, XMR, SOL, ADA, AVAX, DOT, POL, LINK)

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden. It discloses output contents (fair value gap, valuation category) and the data source, giving a clear picture of the tool's behavior. It lacks mentions of limitations or side effects, but for a read-only lookup this is reasonably transparent.

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?

Three sentences, each earning its place: the first states the purpose and outputs, the second explains the metric, and the third cites the data source. Front-loaded with the action verb, with no unnecessary words.

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 single-parameter tool with no output schema, the description effectively explains what the tool returns and the meaning of TVR Price. It could mention edge cases like unknown coins, but the provided context is sufficient for a simple lookup.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already provides a comprehensive description for the coin parameter with examples. The description adds only the general context that it applies to a cryptocurrency, offering no additional syntax or constraints beyond what the schema provides.

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 returns TVR's fair value estimate for a cryptocurrency, specifically mentioning the fair value gap and valuation category. This distinguishes it from sibling get_tvr_score, which likely provides a different metric (score vs. fair value).

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 explains the concept behind TVR Price (fundamental quality vs. market price), which implies when it might be useful, but it does not explicitly state when to use this tool over alternatives like get_tvr_score or provide any exclusion criteria.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation4/5

Most tools target distinct functions (listing, scoring, valuation, comparison, rankings, methodology, history). However, get_tvr_estimated_value and get_tvr_score overlap significantly, as get_tvr_score already includes the valuation data. Compare_coins and get_comparison_report are similar but differentiated by depth.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern, primarily using 'get_' with a descriptive noun. This makes the tool names predictable and easy to navigate.

Tool Count5/5

11 tools is well-scoped for a cryptocurrency analysis service, covering the full range of querying, comparison, and premium features without excess.

Completeness5/5

The tool set covers the major use cases: discovering coins, obtaining scores and valuations, comparing, ranking, historical tracking, portfolio analysis, and understanding methodology. No significant gaps are apparent.

Resources