Skip to main content
Glama
Sign In

MangroveAI

by io.github.MangroveTechnologies
OverviewDiscussionsAdmin

get_smart_money_dex_trades

Read-onlyIdempotent

Recent DEX trades from smart-money wallets across chains. Returns a paginated list of executed trades with token, side, size and wallet metadata. Use it when the user asks what smart money is trading on DEXs, or wants a raw feed of smart-money swap activity.

[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_dex_trades"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number for pagination.
chainsNoOptional list of chains to include.
filtersNoOptional filter object passed through to the upstream provider.
order_byNoOptional ordering list passed through to the upstream provider.
per_pageNoPage size for pagination.

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

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, idempotent, open-world), so the bar is lower; the description still adds real value by disclosing the access model — 0.02 USDC per call via x402 or an API key, with auto-pay for capable clients. That prevents a failed invocation for an unprepared agent. It omits rate limits, upstream-provider behavior for the pass-through 'filters' object, and error conditions.

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?

Front-loaded with the data returned, then the usage condition, then access mechanics in a bracketed aside that is easy to scan. Two tight paragraphs with no filler, though the access note could be one clause shorter.

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?

There is no output schema, and the description compensates by enumerating the returned trade fields; combined with 100% schema coverage and full annotation coverage on safety, an agent has what it needs to call this correctly. The main remaining gap is semantics for the nested filter/order_by pass-through objects.

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 page, per_page, chains, filters and order_by are already documented in the schema; baseline 3 applies. The description adds only the notion of a paginated list, and says nothing about the nested pass-through objects (filters, order_by), which are the most ambiguous parameters.

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 ('Recent DEX trades from smart-money wallets across chains') and names the returned fields (token, side, size, wallet metadata), so the agent knows exactly what data comes back. It does not explicitly contrast with the closest sibling (get_smart_money_perp_trades), leaving the DEX-vs-perp distinction to be inferred from the word 'DEX'.

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?

Gives a clear usage trigger: 'when the user asks what smart money is trading on DEXs, or wants a raw feed of smart-money swap activity.' That is enough context to select the tool, but it names no alternative and states no conditions under which another tool should be preferred.

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