Skip to main content
Glama

POPULAR (Sui memecoin launchpad)

Wallet holdings

get_wallet
Read-onlyIdempotent

A wallet's SUI balance and the POPULAR-listed tokens it holds, each with amount, price and value 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": {
      "address": "<address>"
    },
    "name": "get_wallet"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesA Sui address, 0x and 64 hex digits.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and non-destructive, so the safety profile is covered. The description adds genuinely non-obvious scoping behavior: only POPULAR-listed tokens are returned, which warns the agent that results may omit tokens the wallet actually holds. It stops short of saying what happens for an empty or unfunded wallet, keeping it below a 5.

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?

One sentence, front-loaded with the balance and then the token list, with no redundant or filler wording. Every clause contributes content the agent needs.

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 one-parameter, annotation-covered read tool with no output schema, the description adequately defines the return shape (balance, token list, amount/price/value). The main remaining gap is the undefined 'POPULAR' list and the empty-wallet case, but neither prevents correct invocation.

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%, and the single parameter's format (0x plus 64 hex digits) is fully documented in the schema. The description adds nothing beyond that about the address parameter, so the baseline of 3 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 states the exact resource returned: a wallet's SUI balance plus the POPULAR-listed tokens it holds, with amount, price, and value. That is specific enough to separate it from siblings like get_token (single token detail) or get_holders (who holds a token), though it is phrased as a noun fragment rather than a verb+resource statement.

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 and no named alternative. An agent gets no signal about when to call get_wallet versus get_holders, get_token, or quote_trade; it must infer the distinction from the resource name 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