Skip to main content
Glama

POPULAR (Sui memecoin launchpad)

Token trades

get_trades
Read-onlyIdempotent

A token's latest trades, newest first (curve trades and pool swaps): side, SUI and token amounts, price, trader, time, digest.

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": {
      "token": "<token>"
    },
    "name": "get_trades"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
tokenYesThe token's POPULAR id (0x…, from search_tokens) or its coin type (0x…::module::NAME).
traderNoOnly this wallet's trades.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so safety is covered. The description adds genuinely new behavioral detail: result ordering (newest first) and the two event classes included (curve trades and pool swaps), which matters because an agent might otherwise assume bonding-curve-only data. It stops short of describing pagination or depth of history.

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?

A single front-loaded sentence with the resource first and a colon-delimited field list, so an agent can stop reading after the opening clause. The field enumeration is dense but each item carries information; nothing is redundant with the annotations.

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, so the description usefully substitutes by enumerating returned fields (side, SUI and token amounts, price, trader, time, digest) and their ordering. Combined with annotations covering the safety profile and the schema covering two of three parameters, an agent has enough to call this correctly; only pagination/limit behavior is left implicit.

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 coverage is 67%; `token` and `trader` are already documented in the schema and the description merely echoes them. The one gap the description partially compensates for is `limit`: by saying results come 'newest first' it implies limit means the N most recent trades, which is real added meaning, but the 1–100 range and default 30 are left to the schema.

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 names a specific resource and scope: a single token's latest trades, returned newest first, covering both curve trades and pool swaps. That verb+resource+scope is clear enough for an agent to act on, but it never names a sibling (e.g. get_candles or get_holders) to distinguish this from other token-history tools.

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

Usage Guidelines3/5

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

Usage is implied by 'a token's latest trades, newest first' — an agent can infer this is for recent-activity inspection rather than price history. But there is no explicit when-to-use, when-not-to-use, or pointer to an alternative for historical or aggregated views, so the agent must infer the boundary itself.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources