Skip to main content
Glama

Feegate AI Agent data marketplace catalog & platform metrics

chain-health.chain_ranking

Read-onlyIdempotent

Ask "which blockchain is healthiest right now" — full: every chain scored on TVL, stablecoins, turnover, gas. | 完整排名:每条链的 TVL、稳定币发行量、DEX 24h 成交、周转率、稳定币/TVL 比、实时 gas、综合评分与四项分位明细。参数同左。

[zh] 供应方资产「公链健康度对比(资金/活跃/成本)」按次计费 $0.09 USDC(或等值积分)。 入参:chain、top、gas。 [en] Vendor asset "公链健康度对比(资金/活跃/成本)". Paid per call: $0.09 USDC (or prepaid credits). Args: chain, top, gas. 付款/支付头在 MCP 请求头里带(X-Payment / X-Payment-Tx / Authorization: Bearer fg_…),不要放进参数。

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": "chain-health.chain_ranking"
  }
}

Input Schema

NameRequiredDescriptionDefault
gasNo
topNo
chainNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), and the description adds genuinely non-structured context: per-call pricing of $0.09 USDC or credits, and the requirement to supply X-Payment / X-Payment-Tx / Authorization Bearer headers in the MCP request headers rather than in parameters. It also discloses the breadth of the response (composite score plus four sub-score breakdowns). It does not state rate limits or failure behavior on unpaid calls, which keeps it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core question is usefully front-loaded, but the body is fragmented across three overlapping sections (English one-liner, Chinese metric list, then [zh]/[en] vendor blocks that restate the same asset and args). '参数同左' is a self-reference with no antecedent, and the duplicate Chinese/English payment paragraphs waste space without adding information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only, no-output-schema ranking tool, the definition does cover what the response contains, the cost, and the payment mechanics, which are the high-risk unknowns. It is incomplete on parameter meaning, on how it differs from chain_now, and on result size/limits for a 'full' ranking over every chain.

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

Parameters2/5

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

Schema description coverage is 0% for all three parameters (chain, top, gas), so the description carries the full burden — but it only repeats the parameter names ('入参:chain、top、gas') and adds a dangling '参数同左' with no explanation of types, units, defaults, or what 'top' limits or whether 'gas' toggles inclusion. An agent must guess at the semantics of every argument.

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 opening line gives a concrete verb-and-resource framing ('which blockchain is healthiest right now' → every chain scored on TVL, stablecoins, turnover, gas), and the Chinese section enumerates the exact metric set returned. It is distinguishable from a quick snapshot by the word 'full', but it never names chain_now, so the boundary with that sibling is left implicit.

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 question-style framing implies when to reach for it ('which chain is healthiest right now'), and the payment note implies a cost-sensitive usage context. However, there is no explicit when-not guidance and no reference to the cheaper/simpler chain_now alternative that a cost-conscious agent would want to weigh against a $0.09 call.

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.