Skip to main content
Glama

DeFi Capital Flow-Price Gap

Holder value today (paid, x402)

get_holder_value
Read-only

Holder value for 10 DeFi tokens on Ethereum: revenue, burn, buyback, payouts, dilution and net, first-party on-chain. Bitcoin-timestamped; free proof: /verify/index.json. Informational, not investment advice. Paid: $0.02 USDC on Base with x402 inside the MCP call (_meta["x402/payment"]); without payment the tool returns the x402 PaymentRequired result and nothing is charged. Same JSON as GET /v1/holder-value.

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_holder_value"
  }
}

Input Schema

NameRequiredDescriptionDefault
receiptNooptional: refetch.receipt from an earlier paid answer of the same tool - the same data again without payment (terms 2b)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the paid cost ($0.02 USDC on Base), the x402 payment mechanism embedded in the MCP call, and the consequence of no payment (PaymentRequired result, no charge). It also notes Bitcoin-timestamped data, a free proof endpoint, and the informational-only disclaimer, giving an agent strong behavioral context for a non-idempotent read tool.

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?

The description is dense but front-loads the core purpose and then covers timestamping, proof, disclaimer, payment, and API equivalence in a compact space. Semicolon-heavy sentences reduce readability slightly, but no sentence is extraneous.

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?

Given the tool has one optional parameter, no output schema, and annotations covering safety hints, the description is nearly complete: it explains what data is returned, payment behavior, error handling, and proof availability. It could better describe the fixed set of tokens or the return structure, but it is sufficient for correct invocation.

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?

Schema description coverage is 100%, so the optional receipt parameter is already fully documented in the schema. The description does not mention or add meaning to the receipt refetch behavior, so the baseline of 3 is appropriate.

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?

The description clearly states it provides holder value for 10 DeFi tokens on Ethereum and enumerates the components (revenue, burn, buyback, payouts, dilution, net). This is specific enough to distinguish it from generic signal tools, but it does not explicitly differentiate itself from siblings like get_token_signal or get_signal.

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?

Usage context is implied by the data it returns and the payment condition, but there is no explicit guidance on when to choose this tool versus free siblings such as get_free_signal or list_free_days. The payment requirement is stated, which helps an agent understand a precondition, but alternatives are not named.

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.

Resources