Skip to main content
Glama

SouthPow crypto & market data

buy_tok_PRIORS

Paid. Priors Agents (PRIORS) 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/PRIORS.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 burden and does well: it discloses that the call is paid ($0.01 USDC on Base or Solana), requires no account or API key, and that failed calls are not charged. The gap is that it does not explain how the payment is actually transacted or settled before the call succeeds.

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.' followed by the returned fields, price, access terms, and the endpoint URL — dense and largely waste-free. The bare URL at the end is slightly raw but still informative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output format is described inline (three fields) which is adequate given no output schema, and cost/access are covered. However, for a paid tool with no annotations, the mechanics of paying (how USDC is sent, whether payment precedes or follows the request) are left entirely unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are zero parameters and the schema is an empty object, so the baseline is 4, but the description implies a fixed resource with no configurable options yet never explicitly confirms that no inputs are needed. A 3 reflects that small unstated inference rather than a real deficiency.

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 specific resource (Priors Agents / PRIORS) and the exact payload returned: live USD price, 24h change, and market-cap rank. It clearly distinguishes itself from the many buy_coin_*/buy_tok_* siblings by naming the token, though it does not contrast with generic siblings like buy_crypto_price.

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 never says when to use this over buy_crypto_price or the buy_coin_PRIORS-style alternatives, nor what conditions warrant paying. The only usage-adjacent statement is access logistics ('No account, no API key'), which is not selection guidance.

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