Skip to main content
Glama
Sign In

MangroveAI

by io.github.MangroveTechnologies
OverviewDiscussionsAdmin

get_token_dex_trades

Read-onlyIdempotent

DEX trades for a specific token across all participants in a date window. Returns raw swap events with wallet, size and pool metadata; useful for post-hoc flow analysis on a single token. Native ETH is read as WETH, and the token must be deployed on the chain asked for.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number for pagination.
chainNoChain name or slug, e.g. ethereum or base.ethereum
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

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that: the return shape (raw swap events with wallet/size/pool metadata), the WETH normalization for native ETH, and notably the dual access model (0.02 USDC via x402 PAYMENT-SIGNATURE header, or API key with no per-call charge). It still says nothing about rate limits, pagination limits, or how large a result set can be.

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?

Two compact paragraphs, front-loaded with what the tool returns and why it matters, followed by the access/payment bracket. Every sentence carries information an agent needs; nothing is redundant with the name or the schema.

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?

For an 8-parameter tool with nested objects and no output schema, the description covers the return concept and access model but leaves the most opaque surface unexplained: what goes inside the passthrough filters and order_by objects, and how pagination (page/per_page) behaves. An agent can call it correctly for the common case but has no guidance for the flexible filtering path.

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, and the description earns an extra point by clarifying semantics the schema does not: native ETH is normalized to WETH (affecting the symbol parameter) and the token must be deployed on the requested chain (affecting chain). The date window is described only generically, and the opaque filters/order_by pass-through objects are not illuminated at all.

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?

The description gives a specific verb and resource ('DEX trades for a specific token') plus a scope qualifier ('across all participants in a date window') and states what is returned ('raw swap events with wallet, size and pool metadata'). That scope phrase implicitly separates it from the smart-money variant, but no sibling is named, so the differentiation is left to inference rather than stated.

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?

It provides a clear use context ('useful for post-hoc flow analysis on a single token'), which tells an agent this is an exploratory/analytical read rather than a live signal lookup. It also states a precondition ('the token must be deployed on the chain asked for'), but never names an alternative tool or an explicit when-not-to-use condition.

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