Skip to main content
Glama

SouthPow crypto & market data

buy_tok_PGOLD

Paid. Pleasing Gold (PGOLD) 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/PGOLD.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior3/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 on the commercial/operational side: price, payment rails, no auth needed, and no charge on failure. It leaves out response format, latency/freshness guarantees, and rate limits, which 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with 'Paid.', then the payload, then cost/rails, auth, billing policy, and the endpoint URL in a single dense line. Every fragment carries operational information; no filler.

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 parameterless single-asset price lookup with no output schema, the description covers what is returned, what it costs, and how to pay. Minor gap: it doesn't say whether the response is JSON or how the market-cap rank is formatted, but nothing would block a correct call.

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 the baseline is 4; the tool takes no inputs and the description correctly implies a fixed, parameterless fetch. Nothing is added or needed beyond the empty schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete resource (Pleasing Gold / PGOLD) and exactly what it returns: live USD price, 24h change, market-cap rank. Because the token ticker is the only differentiator among hundreds of buy_tok_* siblings, naming PGOLD explicitly is what makes the tool selectable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear calling context: it is paid ($0.05 USDC), payable on Base or Solana, requires no account or API key, and failed calls are not charged. It stops short of naming an alternative (e.g. the generic buy_crypto_price or buy_coin_* token tools) or stating when not to use it, so no explicit sibling routing.

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