Skip to main content
Glama

POPULAR (Sui memecoin launchpad)

Build a limit order (unsigned)

build_limit_order
Read-only

Unsigned limit order (popular_orders): escrows SUI (buy) or tokens (sell) until the market gives price SUI per token or better; 0.3% fee; expires after days. For POPULAR and SuiPump tokens.

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

Input Schema

NameRequiredDescriptionDefault
daysNo
sideYes
priceYesSUI per whole token (not tokens per SUI).
tokenYesThe token's POPULAR id (0x…, from search_tokens) or its coin type (0x…::module::NAME).
amountNoBuy: SUI (at least 1). Sell: tokens.
senderYesA Sui address, 0x and 64 hex digits.
percentNoSell: share of the balance.
acceptCrossingNoAllow a price more than 10% through the market (it fills at once at the order's price).

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 readOnlyHint=true and destructiveHint=false, and the description is consistent with that by flagging the output as unsigned. It adds genuinely non-obvious behavior: funds are escrowed until the price condition is met, a 0.3% fee applies, the order expires after `days`, and the token scope is restricted to POPULAR and SuiPump. What is missing is what exactly is returned (transaction bytes for signing) and whether anything happens on-chain at build time.

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?

A single dense sentence that front-loads the essential framing ('Unsigned limit order') and then packs escrow direction, price condition, fee, expiry, and token scope without a wasted clause. Every element maps to something an agent needs before calling the tool.

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 build tool with no output schema, the definition covers the important economics (escrow, fee, expiry, price direction) but never states what it returns — presumably an unsigned transaction for the caller to sign and submit — which matters because that determines the agent's next step. It is adequate rather than complete for a tool of this complexity.

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 75%, so the schema already documents sender, token, price, amount, percent, and acceptCrossing. The description adds the ordering semantics ('price SUI per token or better') and ties `days` to expiry, but does not meaningfully explain amount vs. percent interplay or the acceptCrossing threshold beyond what the schema states. Baseline 3 is right when the schema carries most of the load.

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 ('unsigned limit order (popular_orders)') and pins the mechanism: SUI escrowed on buy, tokens on sell, filling at `price` SUI per token or better. Scope is narrowed to POPULAR and SuiPump tokens, so the agent knows the universe of applicability. It stops short of naming when to prefer this over the sibling build_buy/build_sell market-order paths, which keeps it from a 5.

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?

Implied usage is clear from the mechanics — use this when the user wants a resting order at a target price rather than an immediate fill — and the '0.3% fee' plus 'expires after `days`' framing helps an agent set expectations. However, there is no explicit when-to-use/when-not statement and no named alternative for market execution. Given build_buy and build_sell exist in the sibling set, the missing routing sentence is a real gap.

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