Skip to main content
Glama

POPULAR (Sui memecoin launchpad)

Quote a trade

quote_trade
Read-onlyIdempotent

What a buy or sell would do now, without building it: route (POPULAR curve, SuiPump curve or DEX aggregator), amount paid, expected and minimum received, fees, price and price impact.

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

Input Schema

NameRequiredDescriptionDefault
sideYes
tokenYesThe token's POPULAR id (0x…, from search_tokens) or its coin type (0x…::module::NAME).
amountNoBuy: SUI to spend. Sell: tokens to sell. Whole units as a decimal, e.g. "1.5".
senderNoOptional: the wallet's fee tier and, for percent, its balance.
percentNoSell only: a share of `sender`'s balance instead of amount.
slippageBpsNoSlippage tolerance in basis points (500 = 5%).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, open-world behavior. The description adds valuable behavioral detail about what the quote returns, including route source, amount paid, expected and minimum received, fees, and price impact. It does not discuss quote freshness or failure modes.

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?

It is a single front-loaded sentence with a colon-delimited list of outputs. There is no filler, and each clause specifies useful information.

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?

For a read-only quote tool with no output schema, the description covers the important return fields and the non-building nature of the call. Minor gaps around quote freshness and explicit routing to build tools remain, but the core invocation needs are covered by description plus schema.

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 83%, so the schema already documents most parameters including amount, sender, percent, and slippage. The description adds little parameter-level meaning beyond buy/sell context and output contents.

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 states a concrete action: quote what a buy or sell would do now, and enumerates the outputs such as route, amounts, fees, and price impact. The phrase 'without building it' implicitly distinguishes it from the build_* siblings, but does not name them.

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?

It implies this is a preview to use before constructing a trade by contrasting with building it, but never explicitly says to use this before build_buy or build_sell. No exclusions, prerequisites, or alternative-selection guidance are stated.

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