Skip to main content
Glama

POPULAR (Sui memecoin launchpad)

Search tokens

search_tokens
Read-onlyIdempotent

Find tokens on POPULAR by name, ticker ($ optional) or contract (coin type, package or POPULAR id). Returns up to 20 matches with id, symbol, coin type, status and market cap in SUI.

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": {
      "query": "<query>"
    },
    "name": "search_tokens"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesName, ticker or contract.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered structurally. The description adds the result cap ('up to 20 matches') and the returned field set including market cap denominated in SUI, which is genuine added context. It says nothing about matching semantics, ranking, or what happens on zero matches.

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?

Two sentences, no filler, with the accepted query forms front-loaded before the return contract. Every clause carries information an agent needs to construct a query or interpret the result.

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-shape burden, and it does list the fields and the 20-result ceiling. Gaps remain around matching behavior (exact vs. prefix vs. fuzzy) and the absence of pagination or offset guidance, but for a one-parameter read tool this is close to sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3, and the description goes beyond the schema's bare 'Name, ticker or contract' by clarifying that the ticker may carry an optional '$' prefix and that 'contract' means coin type, package id, or POPULAR id. That clarification materially reduces malformed-query risk.

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 ('Find tokens on POPULAR') and enumerates accepted identifier forms (name, ticker with optional $, contract via coin type, package or POPULAR id), which distinguishes it from the single-token get_token sibling by implication. It stops short of naming that sibling or stating the search vs. lookup boundary explicitly.

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 only implied by the search framing; there is no explicit when-to-use or when-not-to-use statement, and no guidance on preferring get_token once a token id is known. An agent can infer the search role, but nothing in the text routes it away from alternatives.

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