Skip to main content
Glama

SouthPow crypto & market data

buy_tok_USDP

Paid. Pax Dollar (USDP) 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/USDP.

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

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 supplied, the description carries the full behavioral burden and does well: it discloses the paid model, the $0.05 USDC price, the two accepted payment chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged. It stops short of rate limits, latency, or what a failure looks like, but the commercial and auth behaviour is unusually well covered.

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?

Front-loaded with the 'Paid.' marker, then purpose, then cost, then access terms, then endpoint. Every clause carries information an agent needs; nothing is redundant or 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?

For a zero-parameter, single-asset price call with no output schema, the description covers what is returned, what it costs, and what auth is required. The only real gap is the absence of any routing statement against the very large sibling set, and a brief note on response shape would help since no output schema exists.

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 and the baseline of 4 applies. The description correctly implies no arguments by anchoring the call to a hardcoded asset and endpoint.

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 verb and resource: it returns the live USD price, 24h change and market-cap rank for Pax Dollar (USDP), and pins the exact asset with both name and ticker. It does not differentiate itself from near-neighbours like buy_crypto_price or the buy_coin_* family, so an agent gets a clear purpose but no routing signal.

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 is implied by the fixed asset and the fixed data fields (price, 24h change, rank), and the payment/auth preconditions are spelled out. However, there is no statement of when to prefer this over buy_crypto_price or a buy_coin_* sibling, and no when-not-to-use guidance, which matters in a catalogue this dense.

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