Skip to main content
Glama

SouthPow crypto & market data

buy_tok_PC0000085

Paid. Tradable LatAm Middle-Market Lender SSTL (PC0000085) 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/PC0000085.

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

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 behavioral burden and does a solid job: it discloses that the call is paid, priced at $0.01 USDC, settleable on Base or Solana, requires no account or API key, and that failed calls are not charged. The failure-billing guarantee is exactly the kind of context an agent cannot get from structured fields. It stops short of rate limits, latency, or response format, 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 text is dense and front-loaded: asset identity first, then the returned fields, then pricing/access terms, then the endpoint. The opening 'Paid.' fragment and the run-on price sentence are slightly terse, but every clause (cost, chains, no auth, failure billing) earns its place.

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, single-asset price lookup with no output schema, the description covers what an agent needs: which asset, what fields are returned, what it costs, how to pay, and that failures are free. It lacks a stated response format and rate-limit expectations, which is the remaining gap.

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 no parameter semantics to document and the baseline of 4 applies. The description correctly does not waste space restating an empty schema.

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 specific asset (PC0000085, 'Tradable LatAm Middle-Market Lender SSTL') and states exactly what data comes back: live USD price, 24h change, and market-cap rank. That is enough to distinguish it from the hundreds of other buy_tok_* siblings, but it never relates itself to the near-duplicate buy_tok_PC or to buy_crypto_price, so an agent still has to infer the boundary.

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 identifier and the '$0.01 USDC' framing, and the payment/no-key notes tell the agent it can call without setup. However, there is no explicit statement of when to choose this over the generic buy_crypto_price or a different PC0000xxx token endpoint, so the routing decision is left to inference.

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