Skip to main content
Glama

SouthPow crypto & market data

buy_tok_PATHUSD

Paid. pathUSD (PATHUSD) 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/PATHUSD.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations exist, so the description carries the full burden; it does well on cost ($0.05 USDC), payment rails (Base or Solana), auth (no account, no API key), and billing behavior ('Failed calls not charged'), plus the endpoint URL. It omits rate limits, latency/freshness of the price, and the actual response shape beyond a field list, so the burden is only partly met.

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?

Tight and front-loaded: the paid flag, the payload, the price/rails, the auth and failure terms, then the URL. The telegraphic 'Paid.' opener and the raw URL are slightly terse but each sentence carries distinct decision-relevant information.

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?

With no output schema, the description must describe the return, and it does by enumerating price, 24h change, and market-cap rank; it also covers payment and failure semantics. Missing are response format/units and data freshness, which are minor for a zero-parameter single-value lookup.

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; baseline 4 applies. The coin identity is baked into the endpoint name and URL, leaving no ambiguity about what is being priced.

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 resource and payload: 'pathUSD (PATHUSD) price: live USD price, 24h change and market-cap rank,' which is far more specific than the name alone. It does not, however, distinguish this from the large buy_coin_*/buy_stable_* families or explain why a token price lives under the buy_tok_ prefix.

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

Usage Guidelines2/5

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

It implies usage (fetch PATHUSD market data) and discloses the $0.05 cost, which helps an agent decide, but it names no alternatives and gives no when-not-to-use condition. With hundreds of near-identical sibling price tools, the absence of any routing guidance is a real gap.

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