Skip to main content
Glama
Sign In

MangroveAI

by io.github.MangroveTechnologies
OverviewDiscussionsAdmin

get_smart_money_netflows

Read-onlyIdempotent

Aggregated smart-money netflows across all tokens market-wide: which tokens funds and smart traders are accumulating or distributing. Use it when the user asks what smart money is buying or selling, or wants to see market-wide on-chain trends.

[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

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": "get_smart_money_netflows"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results.
chainsNoOptional list of chains to include.
timeframeNoAggregation window, e.g. 24h, 7d.24h
include_labelsNoSmart-money wallet labels; omitted uses Fund and Smart Trader.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare a read-only, idempotent, non-destructive, open-world operation. The description adds important operational context beyond annotations: payment is required via x402 (0.02 USDC) or an API key, and x402-capable clients auto-pay. It does not describe response shape or rate limits, but the payment/authentication disclosure is valuable.

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?

The description is front-loaded with purpose and usage guidance, then follows with a bracketed access note. Every sentence carries information an agent needs: what is returned, when to call it, and how payment/auth works.

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 no output schema and fully documented optional parameters, the description is sufficient for correct invocation: it states the aggregation scope, use cases, and access mechanism. It could add a bit more about ordering or result shape, but the essential context is present.

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 100%, so `limit`, `chains`, `timeframe`, and `include_labels` are already documented in the schema. The description references funds and smart traders conceptually, matching the default labels, but adds no additional syntax, constraints, or behavior for the parameters beyond what the schema provides.

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?

It states a specific aggregation resource: 'smart-money netflows across all tokens market-wide' and explains that the output shows accumulation vs distribution. The market-wide scope implicitly separates it from token-level siblings, but it does not explicitly name `get_smart_money_flows` or another alternative.

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

Usage Guidelines4/5

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

The description gives clear triggering cases: 'when the user asks what smart money is buying or selling' or wants 'market-wide on-chain trends.' It does not list exclusions or explicitly route the agent to any sibling tool.

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