Skip to main content
Glama
Sign In

Feegate AI Agent data marketplace catalog & platform metrics

by org.feegate
OverviewDiscussionsAdmin

whale-flow.whale_top5_entry

Read-onlyIdempotent

Ask "who just moved a large amount of this token" — top 5 transfers over the last 20 Base blocks with USD value, from/to addresses and tx hash. Entry tier. The full scan report with address profiling is $0.02.

[zh] 供应方资产「大额转账扫描（近 N 块）」按次计费 $0.07 USDC（或等值积分）。 入参：token、chain、blocks、min_usd。 [en] Vendor asset "大额转账扫描（近 N 块）". Paid per call: $0.07 USDC (or prepaid credits). Args: token, chain, blocks, min_usd. 付款/支付头在 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": "whale-flow.whale_top5_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNo
tokenNo
blocksNo
min_usdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, and the description adds genuinely non-structured context: per-call pricing ($0.07 USDC), the prepaid-credit option, and exactly which headers carry payment (X-Payment / X-Payment-Tx / Authorization). Minor ambiguity remains about how the fixed '20 blocks' window relates to the blocks parameter.

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 English opener is well front-loaded and answers the user-phrased question directly. However the [zh] and [en] blocks largely restate the pricing and arg list, adding redundancy rather than new 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?

With no output schema, the description usefully lists the return fields, and for a paid read tool it covers price and payment mechanics. It falls short on parameter semantics and on reconciling the hardcoded '20 blocks' against the null-default blocks parameter.

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 0%, so the schema carries no meaning, yet the description recovers all four argument names (token, chain, blocks, min_usd). It still gives no per-argument semantics — no format, default, or what min_usd filters — so it only partially compensates for the coverage gap.

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?

States a specific verb and resource (top 5 transfers over the last 20 Base blocks) and enumerates the returned fields (USD value, from/to addresses, tx hash). It partially differentiates from the fuller scan by noting 'The full scan report with address profiling is $0.02', though it never names the sibling that provides it.

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?

Implies entry-tier positioning versus the $0.02 full report, and explains payment headers, but gives no explicit when-to-use/when-not guidance and does not name the alternative tool an agent should switch to for profiling.

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

All Feegate AI Agent data marketplace catalog & platform metrics toolsInspect
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.

Resources