Skip to main content
Glama
Sign In

SouthPow API

by media.southpow
OverviewDiscussionsAdmin

buy_tok_ATOS

Paid. Atoshi (ATOS) 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/ATOS.

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

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 disclosure burden and does solid work: it flags the tool as paid, quantifies the charge ($0.01 USDC on Base or Solana), states no account or API key is needed, and that failed calls are not charged. Missing only the mechanics of how payment is attached to the call.

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 critical 'Paid' flag, then the purpose, then cost and access terms, ending with the endpoint. Telegraphic phrasing is dense but every clause carries information; only the raw URL feels slightly gratuitous.

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-param, no-output-schema price lookup, the description covers what is returned, cost, chains, auth requirements, and failure billing. A note on the expected payment flow would close the last gap, but an agent has enough to decide and invoke.

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 disambiguate; the schema is empty and complete. Baseline 4 applies.

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 (Atoshi/ATOS) and enumerates what is returned: live USD price, 24h change, and market-cap rank. That is far more precise than the bare tool name. It doesn't explicitly contrast with siblings like buy_crypto_price or buy_coin_* entries, but the token scope 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implicit usage is clear from 'Paid' plus the cost and payment rails, so an agent knows this is a per-call paywalled lookup. However, it never states when to choose this over the many sibling price tools (buy_crypto_price, buy_coin_*), nor any prerequisite ordering for the payment step.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SouthPow API toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources