Skip to main content
Glama

SouthPow crypto & market data

buy_tok_PC0000049

Paid. Tradable Eu/LatAm PoS Financing SSTL (PC0000049) 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/PC0000049.

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

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?

No annotations, so the description must carry the load, and it does: cost, payment chains, no auth needed, and a refund policy for failed calls. What's missing is data freshness/latency and rough response shape, which matters for a live price tool.

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?

Front-loads the critical fact (paid), then the payload, then price/auth policy, then endpoint URL. Dense and essentially waste-free, though the inline endpoint URL is arguably redundant and the sentence construction is a run-on.

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, no-output-schema lookup, the description tells the agent what it returns, what it costs, how to pay, and that failures are free — enough to call safely. Only response shape and data staleness are left unaddressed.

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?

Zero input parameters with 100% schema coverage, so there is nothing for the description to clarify about inputs. Baseline applies; the description correctly makes clear the token is baked into the tool 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?

States a specific resource (price for PC0000049) and enumerates the payload: live USD price, 24h change, market-cap rank. The token identifier distinguishes it from the long list of sibling buy_tok_* tools, but there's no explicit statement of how it differs from the generic 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?

Covers prerequisites well (paid, $0.05 USDC on Base or Solana, no account/API key), which is genuine when-to-use context. However, it never says when to pick this over buy_crypto_price or the other buy_tok_ variants, and there are no exclusion criteria.

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