Skip to main content
Glama

POPULAR (Sui memecoin launchpad)

Token details

get_token
Read-onlyIdempotent

One token: name, symbol, coin type, venue, status (curve, graduated…), price and market cap in SUI, 24 h volume, trades and change, holders, curve progress, token check, links and pool.

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

Input Schema

NameRequiredDescriptionDefault
tokenYesThe token's POPULAR id (0x…, from search_tokens) or its coin type (0x…::module::NAME).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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 covered and the description need not restate it. The field list adds domain context the annotations cannot convey (lifecycle states such as curve/graduated, curve progress, token check, pool data), but it says nothing about data freshness, caching, or what happens for an unknown or malformed token.

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?

It is a single, dense sentence with zero filler, and the identifying fields (name, symbol, coin type, venue) are front-loaded before pricing and market data. The trade-off is that the compressed noun-phrase list reads as a fragment rather than a stated action, slightly blunting front-loading of purpose.

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?

With no output schema, this field enumeration is the only documentation of the return payload, which is genuinely necessary and mostly delivered. However, for a lookup tool it omits error behavior for invalid tokens and whether markdown/units or nulls should be expected in fields like venue or pool, leaving modest gaps.

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 100% and the single `token` parameter is already documented as accepting a POPULAR id or a coin type, including the 0x…::module::NAME format. The description adds no meaning beyond that, so the baseline of 3 for fully covered, single-parameter schemas applies.

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 makes clear this returns detail for a single token, and the enumerated fields (name, symbol, coin type, venue, status, price, market cap in SUI, volume, holders, pool) sharply distinguish it from list-style siblings. It never names a sibling (e.g., search_tokens vs. get_holders) and starts with a noun fragment rather than a verb, so the retrieval action is only implied.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no exclusions, and no named alternative. The only routing hint ('from search_tokens') lives in the schema parameter description, not in the tool description itself, so an agent gets no in-description instruction about how to obtain a valid `token` value or which sibling to prefer.

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