Skip to main content
Glama
Sign In

MangroveAI

by io.github.MangroveTechnologies
OverviewDiscussionsAdmin

get_smart_money_flows

Read-onlyIdempotent

One-token flow intelligence snapshot: returns net USD flows and wallet counts for smart traders, whales, exchanges, fresh wallets and public figures together in ONE response. Use for a trailing-window category summary, including the past 24 hours (timeframe=1d). Do not fetch a separate token-flows page for each category to construct this summary. Timeframe is 5m, 1h, 6h, 12h, 1d or 7d. For explicit start/end dates or paginated flow records use get_token_flows. Native ETH is read as WETH; the token must exist on the requested chain.

[Access: pay 0.02 USDC via x402 (PAYMENT-SIGNATURE header) OR authenticate with an API key. An x402-capable client will auto-pay; API-key clients pay nothing per call.]

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "get_smart_money_flows"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoChain name or slug, e.g. ethereum or base.ethereum
symbolYesAsset symbol, e.g. BTC or ETH.
timeframeNoAggregation window, e.g. 24h, 7d.1d

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive and open-world behavior, so the description's added value is the cost/auth model (0.02 USDC via x402 with PAYMENT-SIGNATURE, or free with API key) and the WETH-normalization rule, both of which materially affect how a call is made. It does not describe failure modes (unknown symbol/chain) or response shape, keeping 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.

Conciseness4/5

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

Purpose and the ONE-response payoff are front-loaded, then usage, then exclusions, then caveats, then the bracketed access note. Every sentence carries information, though the access/payment paragraph is bulky and could be trimmed slightly without losing meaning.

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?

With only 3 parameters, no output schema and annotations covering safety, the description covers what is returned (net flows and wallet counts across five categories), valid windows, sibling routing and payment. Missing only error/edge behavior for nonexistent tokens or chains, which prevents a 5.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds real semantics: it enumerates the valid timeframe values (5m, 1h, 6h, 12h, 1d, 7d) where the schema only says 'e.g. 24h, 7d', and it explains the WETH substitution for 'ETH' symbols. It adds nothing for chain beyond the schema's own examples.

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?

States a specific verb and resource (net USD flows plus wallet counts for smart traders, whales, exchanges, fresh wallets and public figures) for a single token, and explicitly contrasts itself with per-category token-flow pages and get_token_flows. An agent can distinguish it from get_smart_money_netflows and get_token_flows without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use ('trailing-window category summary, including the past 24 hours'), an explicit anti-pattern ('Do not fetch a separate token-flows page for each category'), and a named alternative for the other case ('For explicit start/end dates or paginated flow records use get_token_flows'). It also states prerequisites (token must exist on the requested chain, native ETH is read as WETH).

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

All MangroveAI 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