Skip to main content
Glama

SouthPow crypto & market data

buy_tok_PC0000015

Paid. Tradable NA Third Party Online Merchant SSTN (PC0000015) 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/PC0000015.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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 well: it discloses the billing model, price, accepted chains, no-account/no-API-key auth, and the 'failed calls not charged' refund policy. It omits rate limits, latency/freshness of the 'live' price, and whether responses are cached — gaps that matter for a paid per-call endpoint.

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-loaded with 'Paid.' and then the data returned, followed by the practical call details — a sensible ordering with no filler sentences. The trailing raw URL is somewhat redundant for an MCP agent but is arguably useful provenance information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema and no annotations, so the description must stand alone; it compensates by enumerating the three returned fields and the payment mechanics. However, it says nothing about response format, data freshness, or how payment is actually executed (prepaid balance vs. per-call settlement), which are significant gaps for a paid data tool.

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 to disambiguate and the baseline of 4 applies. The description correctly signals that the asset and payment chain are fixed rather than passed as arguments.

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 asset ('NA Third Party Online Merchant SSTN (PC0000015)') and the exact payload returned ('live USD price, 24h change and market-cap rank'), so an agent knows precisely what it gets. It does not explain how this differs from the sibling buy_tok_PC or the buy_coin_* / buy_crypto_price family, so it stops short of 5.

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?

It establishes the precondition for calling (paid, $0.05 USDC on Base or Solana), which implicitly frames usage, but never says when to pick this over buy_crypto_price or the generic buy_tok_PC sibling. No exclusions or alternatives are named.

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