Skip to main content
Glama

SouthPow crypto & market data

buy_tok_SUIUSDE

Paid. eSui Dollar (SUIUSDE) price: live USD price, 24h change and market-cap rank. $0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/SUIUSDE.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "buy_tok_SUIUSDE"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does a good job: it discloses the $0.01 USDC charge on Base or Solana, that no account or API key is needed, and that failed calls are not charged. That is meaningful commercial/behavioral context beyond the schema. It stops short of describing response shape or data freshness guarantees beyond 'live'.

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?

The leading 'Paid.' flag is front-loaded and useful, followed by what is returned, the price, and the access terms. Every clause carries information, though 'No account, no API key' is mildly redundant and the bare URL is of limited use to an agent.

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 zero-param, no-output-schema price lookup, the description covers the asset, the returned fields, the cost, the payment chains, and the failure-charging policy. An agent has enough to decide and to warn a user about the charge; only the response format remains unspecified.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. The token is fixed in the tool identity and confirmed by the '(SUIUSDE)' annotation in the description.

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?

Names the specific asset (eSui Dollar / SUIUSDE) and the exact data returned: live USD price, 24h change, market-cap rank. That is far more specific than a generic 'get token price' and lets an agent match it to the token in the name. It does not explicitly contrast with the many sibling buy_tok_*/buy_coin_* price tools, so it stops short of a 5.

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 description makes clear this is a paid quote for one specific token, and the payment terms imply 'use when you need this token's price'. However it never states when to prefer it over buy_crypto_price or a sibling token tool, nor any prerequisites beyond payment. Usage context is implied rather than spelled out.

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