Skip to main content
Glama

SouthPow crypto & market data

buy_tok_PC0000023

Paid. Tradable Singapore Fintech SSL (PC0000023) 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/PC0000023.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses that the call is paid, the exact cost ($0.01 USDC), the accepted chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged. Missing are rate limits, payment mechanics (how the charge is settled), and response shape, which keeps it from 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is short and front-loaded: cost/paid status first, then the resource and returned fields, then payment and auth terms, then the endpoint URL. It is telegraphic but every clause carries information; the raw URL is arguably clutter for an agent that never needs to call it directly.

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-argument, side-effect-free price lookup with no output schema, the description covers what is returned, what it costs, how payment works, and failure billing. A brief note on response format or data freshness would close the remaining gap, but nothing essential for a correct call is missing.

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

Parameters5/5

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

The tool takes zero parameters, so there is no parameter meaning to convey; the schema is empty and consistent with the description. Nothing is left ambiguous about inputs, and the target token is baked into the tool name and description rather than passed as an argument.

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 names the exact resource (Singapore Fintech SSL token PC0000023) and enumerates the returned fields: live USD price, 24h change, and market-cap rank. The verb is implicit rather than stated ('get/fetch'), and differentiation from the ~700 sibling buy_tok_* tools rests only on the embedded token ID rather than an explicit rule, but an agent can tell what this call produces.

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: fetch this when you need the price of PC0000023. There is no explicit when-to-use versus sibling price tools (e.g. buy_crypto_price, buy_tok_PC), no note on staleness or when to prefer a different source. Payment terms do help the agent decide whether to spend, which is a partial substitute for routing guidance.

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