Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ONE

Paid. ONEchain (ONE) 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/ONE.

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

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 present, the description carries the full load and does well: it discloses that the call is paid ($0.01 USDC on Base or Solana), that no account or API key is required, and that failed calls are not charged. It stops short of explaining how the payment is executed (e.g. 402 handshake) or any rate limits, which keeps it at 4.

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?

Four short telegraphic sentences, front-loaded with the payment gate before the payload and terms. Every clause carries information, though the staccato fragments ('Paid.', a bare URL) read slightly like a listing rather than prose.

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?

No output schema exists, and the description compensates by enumerating the returned fields (USD price, 24h change, market-cap rank). Payment model and cost are also covered; the remaining gap is the mechanics of actually paying/settling the request, which an agent calling a paid endpoint would benefit from knowing.

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 schema has zero parameters, which is the baseline-4 case; there is nothing for parameters to disambiguate. The description implicitly confirms no input is needed beyond selecting this tool, consistent with the empty properties object.

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?

Names the exact asset (ONEchain / ONE) and the exact payload ('live USD price, 24h change and market-cap rank'), so an agent knows this is a single-asset price lookup rather than an audit, yield or FX endpoint. It does not explicitly say how it differs from generic siblings like buy_crypto_price, so it falls short of a 5.

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 implied by the single-asset naming and the 'Paid / $0.01' framing, which signals this is a purchase rather than a free lookup. There is no explicit when-to-use or when-not-to-use statement relative to the many sibling price tools, and no note on whether repeat calls are needed or cacheable.

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