Skip to main content
Glama

POPULAR (Sui memecoin launchpad)

Build a buy (unsigned)

build_buy
Read-only

Unsigned transaction buying a token with SUI, for sender's wallet to sign: base64 bytes, summary (paid, expected and minimum tokens, fees) and a dry run on chain. Does not sign or send anything.

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>",
      "amount": "<amount>"
    },
    "name": "build_buy"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesThe token's POPULAR id (0x…, from search_tokens) or its coin type (0x…::module::NAME).
amountYesSUI to spend, e.g. "1.5".
senderYesA Sui address, 0x and 64 hex digits.
slippageBpsNoSlippage tolerance in basis points (500 = 5%).
maxImpactBpsNoPool routes: most price impact accepted (default 1500).

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 readOnly, openWorld and non-destructive, so the bar is lower; the description adds real value by disclosing the return payload (bytes, summary with paid/expected/minimum tokens and fees, on-chain dry run) and the no-sign/no-send boundary. It does not explain why idempotentHint=false matters — that quotes are state-dependent and the bytes may differ or expire between calls — which is the one behavioral trait an agent most needs.

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 a colon-delimited output list — no filler and the key constraint ('does not sign or send') lands at the end for emphasis. Slightly dense as one run-on sentence, but nothing is wasted.

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?

With no output schema, the description carries the return-value burden and does so adequately by enumerating bytes, summary and dry run. Gaps remain around freshness/expiry of the built transaction and failure modes (e.g., what a failed dry run yields), which matter for a build-and-sign flow.

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 the schema already documents token, amount, sender, slippageBps and maxImpactBps. The description's mention of 'expected and minimum tokens' and 'fees' loosely ties to slippage, but adds no syntax, format or default guidance beyond the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — 'Unsigned transaction buying a token with SUI' — and immediately scopes the output ('base64 bytes, summary ... and a dry run on chain'). This inherently separates it from build_sell and build_limit_order, and the closing 'Does not sign or send anything' prevents confusion with any submit/execute step.

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 rather than stated: the phrase 'for `sender`'s wallet to sign' tells the agent this is a pre-signing step, but there is no explicit guidance on when to prefer this over quote_trade for a preview, nor any prerequisite such as needing a SUI balance or a prior search_tokens lookup. No exclusions or alternatives are named.

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