Skip to main content
Glama

POPULAR (Sui memecoin launchpad)

Build a sell (unsigned)

build_sell
Read-only

Unsigned transaction selling a token for SUI, for sender's wallet to sign: base64 bytes, summary and a dry run. Give amount (tokens) or percent of the balance.

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

Input Schema

NameRequiredDescriptionDefault
tokenYesThe token's POPULAR id (0x…, from search_tokens) or its coin type (0x…::module::NAME).
amountNoTokens to sell, whole units.
senderYesA Sui address, 0x and 64 hex digits.
percentNo
slippageBpsNoSlippage tolerance in basis points (500 = 5%).
maxImpactBpsNo

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; the description reinforces this by making clear the transaction is unsigned and must be signed by the sender's wallet, i.e. nothing is submitted on-chain. It also discloses the return payload. It does not explain what protections slippageBps/maxImpactBps give or what happens when the sale is rejected.

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?

Two tight sentences, front-loaded with what the tool produces and followed by the parameter choice. The colon-list construction is dense but readable; nothing is redundant.

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 six-parameter builder with no output schema, the description covers the return shape (base64 bytes, summary, dry run) and the amount/percent choice. The notable gap is `maxImpactBps`, which is undocumented in both schema and description, and there is no mention of how slippage protections behave.

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%, so baseline is 3. The description adds genuine meaning by presenting `amount` and `percent` as mutually exclusive alternatives with units ('tokens', 'percent of the balance'), which the schema does not state. However, `maxImpactBps` has no schema description and is not explained here either, leaving a real gap.

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: builds an unsigned transaction selling a token for SUI, and describes the output (base64 bytes, summary, dry run). It does not explicitly name build_buy or quote_trade as the directional alternative, but 'selling a token for SUI' is specific enough to separate it from a buy builder.

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?

The phrase 'for `sender`'s wallet to sign' implies the workflow (generate, then sign externally), and 'Give `amount` ... or `percent`' hints at a choice. But there is no explicit guidance on when to use this versus quote_trade first, nor on error conditions or prerequisites such as having a balance.

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