Skip to main content
Glama

SouthPow crypto & market data

buy_tok_OHO

Paid. OHO Blockchain (OHO) 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/OHO.

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

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, the description does real work: it discloses the paid model, the exact price and accepted payment rails (USDC on Base or Solana), that no account or API key is required, and that failed calls are not charged. Missing only rate limits and response format, which keeps it short of 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Six short clauses, front-loaded with the paid flag and the resource, with the billing caveat placed right after the cost. The telegraphic style ('Paid.', a bare URL) is dense but slightly clipped rather than elegantly structured.

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 no-parameter paid tool with no output schema, the description covers what is returned (three named fields), the cost, the payment rails, and the no-auth requirement. It stops short of describing response shape or data freshness, which an agent paying per call might want.

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 the baseline is 4 and there is no parameter semantics to compensate for. The description correctly adds nothing extraneous about inputs.

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 a specific resource (OHO Blockchain price) and enumerates the exact fields returned: live USD price, 24h change, and market-cap rank. It is clearly distinguishable from the buy_coin_* family since there is no buy_coin_OHO sibling, though it never explains the tok-vs-coin naming split that surrounds it.

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 rather than stated: the agent learns this is a paid call at $0.01 USDC, which frames a cost/benefit decision, but there is no explicit when-to-use guidance or named alternative (e.g., buy_crypto_price) for a general price lookup. For a zero-parameter single-purpose endpoint the omission is tolerable but not helpful.

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