Skip to main content
Glama

SouthPow crypto & market data

buy_tok_SURPLUS

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/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 disclose key behavior: it is a paid call costing $0.05 USDC on Base or Solana, requires no account or API key, and failed calls are not charged. That is solid commercial context, but it omits rate limits, latency, and whether the returned price is cached or real-time at call time.

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?

Telegraphic but dense and front-loaded: the paid nature and the returned data come first, followed by price, payment rails, and access conditions. Every fragment carries information; the raw URL at the end is of marginal use to an agent but harmless.

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 parameterless, annotation-free price lookup with no output schema, the description covers the essentials: what data comes back, the cost and payment chains, and the no-signup access model. Only return-format specifics and freshness guarantees are absent, which is acceptable at this complexity.

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 the baseline is 4; there is no parameter meaning left to explain beyond the token being fixed to SURPLUS.

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 (SURPLUS token price) and enumerates the returned fields: live USD price, 24h change, market-cap rank. The token identity is clear and matches the tool name, though it offers no differentiation from adjacent families like buy_crypto_price or buy_coin_* that an agent would have to disambiguate on its own.

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 explicit when-to-use or when-not-to-use guidance and no named alternative, which matters given hundreds of sibling buy_tok_* and buy_coin_* tools. Prerequisites (no account, no API key) are stated, but those are access conditions rather than selection 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