Skip to main content
Glama

SouthPow crypto & market data

buy_tok_PROM

Paid. Prom (PROM) 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/PROM.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does most of the job well: it discloses that the call is paid ($0.05 USDC), payable on Base or Solana, requires no account or API key, and that failed calls are not charged. That is exactly the operational context an agent needs before spending money. It stops short of 5 by not saying whether repeated calls are billed each time or whether the price is a snapshot at call time.

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?

Information is front-loaded and dense: cost and access constraints before the endpoint URL. Every clause adds a distinct fact (price fields, price paid, chain, auth, failure billing), so nothing is padding. The bare URL at the end is the least useful element for an agent but is not harmful.

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 paid lookup with no output schema, the description covers the essentials: what data comes back, what it costs, how payment works, and the failure-billing policy. The remaining gap is the response shape and whether the quote is a point-in-time snapshot, which matters because the agent cannot inspect an output schema.

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 no parameter meaning to add and the baseline of 4 applies. The description correctly implies the token is fixed by the tool identity rather than passed in, which prevents an agent from trying to supply a symbol argument.

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 (Prom/PROM) and enumerates exactly what is returned: live USD price, 24h change, market-cap rank. That is far more than a restatement of the name. It falls short of 5 because the crowded buy_tok_* / buy_coin_* / buy_crypto_price sibling set is never acknowledged, so the agent cannot tell from this text why buy_tok_PROM is preferred over a generic price tool.

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 only implied: if you want PROM's price, call this. There is no explicit statement of when to use it versus buy_crypto_price or a buy_coin_PROM-style sibling, and no exclusions (e.g., no historical data). The cost and payment details tell the agent what it is committing to, which is a partial substitute for routing 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