Skip to main content
Glama

SouthPow crypto & market data

buy_tok_PC0000089

Paid. Tradable LatAm Residential SSTL (PC0000089) 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/PC0000089.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 it well: it discloses cost and payment rails, that no auth is required, that failures are not billed, and which fields come back. It does not mention rate limits, data freshness guarantees, or the response format, which are the remaining behavioral gaps.

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?

It is very compact and front-loaded, with the paywall marked first and then payload, pricing, auth, billing policy, and endpoint. Every clause conveys a distinct operational fact, and nothing is wasted.

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-parameter price lookup with no output schema and no annotations, the description covers what is returned, cost, auth, and failure billing, which is most of what an agent needs. Missing rate-limit and response-format details keep it short of full completeness.

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 of 4 applies. The asset identity is baked into the tool name and restated in the text, so no parameter-level ambiguity exists.

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 a specific resource (LatAm Residential SSTL, id PC0000089) and states exactly what is returned: live USD price, 24h change, and market-cap rank. It is distinguishable from the hundreds of buy_tok_* siblings because the asset identity is explicit, though it never says how it relates to broader tools like buy_crypto_price.

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 context is implied by the asset name: call this for this specific token's price. Access conditions (paid, $0.01 USDC on Base or Solana, no account/key, no charge on failure) are covered well. There is no explicit when-to-use or when-not-to-use guidance versus alternatives such as buy_crypto_price or a category tool like buy_cp_rwa.

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