Skip to main content
Glama

Feegate AI Agent data marketplace catalog & platform metrics

chain-health.chain_now

Read-onlyIdempotent

Ask "which blockchain is healthiest right now" — free: top 3 chains TVL, stablecoin supply, DEX volume, gas. | 免费档:TVL 前 3 条链的资金/稳定币/成交/gas 四项原始值,加链总数与全市场合计。参数 chain / top / gas 可选。

[zh] 供应方资产「公链健康度对比(资金/活跃/成本)」免费(每日限额按调用方计)。 入参:chain、top、gas。 [en] Vendor asset "公链健康度对比(资金/活跃/成本)". Free (daily per-caller quota). 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_now"
  }
}

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 read-only/idempotent/non-destructive profile, and the description adds real context beyond them: a daily quota per caller and the auth/payment mechanism including which headers to use and the explicit warning not to pass payment in parameters. It stops short of describing response shape or what happens when the quota is exhausted.

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 sentence is well front-loaded, but the text then repeats the same facts in a Chinese block, a [zh] block, and an [en] block, restating the args three times. The redundancy inflates length without adding information an agent needs.

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 3-optional-param, no-output-schema tool it covers what is returned (four raw metric values plus chain count and market totals) and how payment is authenticated, which is the critical part. The remaining gap is parameter behavior at 0% schema coverage, which leaves an agent guessing about valid chain identifiers and the meaning of top/gas.

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%, so the description carries the full burden, yet it only repeats the parameter names (chain / top / gas) without explaining accepted values, defaults, or units. The phrase 'top 3 chains' weakly implies top controls how many chains are returned and that gas is a boolean toggle, but chain naming format and behavior are undocumented.

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 names a concrete question and enumerates the four metrics returned (TVL, stablecoin supply, DEX volume, gas) plus the chain count and market totals, so an agent knows exactly what it gets. It never distinguishes itself from the sibling chain-health.chain_ranking, which is the main reason it falls short of a 5.

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?

It states this is a free tier with a daily per-caller quota and tells the agent where to put payment headers (X-Payment / X-Payment-Tx / Bearer token in the MCP headers, not in arguments), which is genuinely useful. However there is no guidance on when to pick this over chain_ranking or the other *_now siblings, so the usage decision is left implicit.

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.