Skip to main content
Glama

POPULAR (Sui memecoin launchpad)

Price candles

get_candles
Read-onlyIdempotent

A token's OHLC price candles in SUI per token. tf: 1m, 5m, 15m, 1h, 4h, 1d. Returns the last limit buckets.

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_candles"
  }
}

Input Schema

NameRequiredDescriptionDefault
tfNo1h
limitNo
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.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely behavioral detail — the quote unit (SUI per token) and that results are the last `limit` buckets, i.e. most-recent-first windowing. It does not say how gaps/illiquid intervals are handled or what happens with an invalid token.

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 short sentences, front-loaded with the resource and unit, then the timeframe set and windowing rule. No filler or redundant restatement of the title.

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, the description should convey the shape of a returned candle (timestamp plus open/high/low/close/volume) and ordering; it only says 'OHLC price candles' and 'last limit buckets'. Adequate to call the tool, but an agent cannot predict the response structure.

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 only 33%, with just `token` documented, so the description must compensate. It clarifies `limit` as 'the last N buckets' (a real semantic addition) and lists the `tf` values, though those merely repeat the enum; the meaning of each timeframe bucket and the token id formats are left to the schema.

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 resource (a token's OHLC price candles) and the quote denomination (SUI per token), which is enough to separate it from get_trades and get_token. It stops short of explicitly naming a sibling alternative, but the verb+resource is concrete.

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 or when-not-to-use guidance and no mention of alternatives such as get_trades for raw fills versus candles for aggregated price history. The agent must infer the charting/aggregation use case from the word 'candles' alone.

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