Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ON

Paid. Orochi Network (ON) 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/ON.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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 behavioral burden and does so unusually well: it discloses the paid model ($0.01 USDC on Base or Solana), that no account or API key is required, and that failed calls are not charged — the latter being a genuinely important risk fact for an agent deciding to spend. It does not cover rate limits or latency, which keeps it below a 5.

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?

Five short sentences, front-loaded with the 'Paid.' signal so the cost is visible before anything else, then the payload, then the price and access terms, then the endpoint. No filler and nothing buried.

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, single-asset purchase, the description covers what is returned, what it costs, how payment works, failure charging, and the underlying URL — enough to call it correctly. The only gap is response shape and freshness, which is acceptable since no output schema exists but the returned fields are already enumerated.

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 clarify beyond the fact that the asset is baked into the endpoint; the stated URL and asset name confirm the call is fully parameterless. Baseline 4 applies for a zero-parameter tool.

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 states a concrete deliverable for a named asset ('Orochi Network (ON) price: live USD price, 24h change and market-cap rank'), which is specific enough to distinguish it from the hundreds of sibling buy_tok_* tools by ticker. It stops short of a clean verb+resource framing (the tool name says 'buy' while the payload is price data), but the content returned is unambiguous.

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?

There is no when-to-use or when-not-to-use guidance, and no mention of the nearby alternatives such as buy_crypto_price or buy_coin_O that an agent might reasonably pick instead. The only contextual cues are commercial (cost, no account needed), 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