Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ORBIO

Paid. Orbio.so (ORBIO) 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/ORBIO.

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

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 carries the full burden and does well: it declares the tool is paid ($0.05 USDC), names the accepted chains (Base or Solana), states no account or API key is required, and promises failed calls are not charged. The main remaining gap is the response shape/latency and whether repeat calls are billed, which an agent spending real funds would want to know.

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-loads the key fact ('Paid.') before the payload description, then stacks cost, payment rails, auth requirements, billing policy, and endpoint in short clauses. Dense but every clause adds a distinct operational fact; only the raw URL is arguably disposable.

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, no-output-schema tool, the description covers what data comes back (price, 24h change, rank), what it costs, how to pay, and that failures are free — enough for an agent to decide and execute. Missing only output format and freshness/latency guarantees.

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 input schema has zero properties, so there is nothing for the description to disambiguate. The only implicit 'parameter' is the asset itself, which is fixed by the tool name and confirmed in the description text.

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 specific asset (Orbio.so / ORBIO) and the exact data returned: live USD price, 24h change, and market-cap rank. An agent can tell this apart from the buy_coin_* and buy_crypto_price families because the token is pinned in the description. It stops short of an explicit verb phrase like 'fetch the price', relying on the tool name for that.

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?

Implicitly scopes usage to this one asset by naming ORBIO and describing the payload, and the payment prerequisites are stated. However, it never says when to prefer this over the overlapping siblings (buy_coin_ORBIO, buy_crypto_price) or what happens if the same data is needed for another token.

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