Skip to main content
Glama

SouthPow crypto & market data

buy_tok_PC0000019

Paid. Tradable North America PoS Lender SSTN (PC0000019) 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/PC0000019.

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

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 load and does well: it discloses the $0.01 USDC charge, the Base or Solana payment rails, that no account or API key is required, and crucially that failed calls are not charged (retry safety). It stops short of explaining how payment is actually settled or what a failure looks like.

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.' then the data payload, then cost, then access terms, then endpoint URL. Every clause carries information; the middle sentences are dense but not padded.

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?

There is no output schema, so the description must state returns — it names price, 24h change and market-cap rank. Combined with the pricing and access terms, an agent has enough to decide to call it; only the response shape and payment flow remain unspecified.

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 parameters, so there is nothing for the description to compensate for and the baseline of 4 applies. The description sensibly spends its words on payload and pricing instead.

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 the resource (price for PC0000019, a North America PoS Lender SSTN) and the returned fields (live USD price, 24h change, market-cap rank). The 'buy_tok_PC0000019' naming among hundreds of buy_tok_* siblings already disambiguates the asset, so the jargon-heavy instrument label doesn't hurt much, but it never explicitly contrasts with buy_crypto_price or buy_tok_PC.

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?

Implies usage through 'No account, no API key' and 'Paid' — the agent learns this is a self-serve paid data call — but there is no explicit when-to-use or when-to-prefer-a-sibling statement, and no note about how to proceed if payment is unavailable.

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