Skip to main content
Glama

SouthPow crypto & market data

buy_tok_PCI

Paid. Paycoin (PCI) 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/PCI.

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

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, the description carries the full burden and does well: it discloses the payment requirement, exact price ($0.05 USDC), accepted chains (Base or Solana), no account/API key needed, and that failed calls are not charged. The main gap is it doesn't describe response shape beyond the three fields mentioned, nor latency/rate limits.

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?

Extremely tight and front-loaded: cost marker first, then what it returns, then payment/failure terms, then the endpoint. No sentence is wasted.

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-param, no-annotation, no-output-schema tool, the description covers purpose, pricing, payment rails, failure policy, and even the URL — enough to call it correctly. Slightly short of 5 because the return value format and error behavior beyond 'not charged' are 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 the baseline of 4 applies; there is nothing for the description to disambiguate in the input schema. The response fields are briefly named instead, which is a reasonable substitution.

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 resource and return set: Paycoin (PCI) live USD price, 24h change, and market-cap rank. Naming the exact token differentiates it from the hundreds of sibling buy_tok_* per-asset tools, though it never explicitly says 'use the matching buy_tok_<SYMBOL> for other coins'.

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?

Implied usage (fetch PCI price) is clear, and the 'Paid / $0.05 USDC' note warns of cost before calling. But there is no explicit when-to-use vs alternatives guidance — nothing distinguishes it from generic siblings like buy_crypto_price or buy_coin_* for this asset.

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