Skip to main content
Glama
Sign In

MangroveAI

by io.github.MangroveTechnologies
OverviewDiscussionsAdmin

get_token_flows

Read-onlyIdempotent

Paginated historical flow records for one non-stablecoin token between explicit start and end dates, optionally filtered by one wallet label. Use for date-range records or pagination. For a trailing-window summary of net USD flows AND wallet counts across categories, use get_smart_money_flows, which returns the categories together in one call. Not available for stablecoins. 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_token_flows"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number for pagination.
chainNoChain name or slug, e.g. ethereum or base.ethereum
labelNoWallet category: smart_money, exchange, whale, public_figure, or top_100_holders.
symbolYesAsset symbol, e.g. BTC or ETH.
date_toNoISO date string for the end of the window.
filtersNoOptional filter object passed through to the upstream provider.
order_byNoOptional ordering list passed through to the upstream provider.
per_pageNoPage size for pagination.
date_fromNoISO date string for the start of the window.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / per_page / default
      Previous value: -100New value: +25
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Goes well beyond the readOnly/idempotent annotations by disclosing the stablecoin restriction, the WETH substitution for native ETH, the chain-existence requirement, and the dual access model with per-call x402 pricing. Missing only return-shape details such as what a flow record contains or pagination limits.

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

Conciseness5/5

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

Front-loads purpose, then alternative routing, then constraints, with a bracketed access note kept separate. Every sentence carries distinct information; no filler.

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?

Covers scope, restrictions, authentication/payment, and the sibling alternative for a 9-parameter tool with nested objects. A small gap remains around the opaque filters/order_by pass-through objects and the structure of returned flow records, though the tool is read-only and low-risk.

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 the baseline is 3, but the description adds real meaning: the date window must be explicit, only one wallet label may be applied, and symbol semantics exclude stablecoins and map native ETH to WETH. The pass-through filters and order_by objects remain unexplained in both schema and description.

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+resource ("Paginated historical flow records") plus scope (one non-stablecoin token, explicit start/end dates, one optional wallet label). An agent can distinguish it from get_smart_money_flows from the text alone.

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?

Explicit when-to-use ("Use for date-range records or pagination") and an explicit alternative with the condition that selects it (get_smart_money_flows for trailing-window net USD flows plus wallet counts in one call). Also states exclusions: not available for stablecoins, token must exist on chain.

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