Skip to main content
Glama

SouthPow crypto & market data

buy_tok_AT

Paid. Apro (AT) 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/AT.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 full burden and does well: it discloses the payment model, exact cost and accepted chains, that no credentials are required, and that failed calls are not charged — a genuinely important billing guarantee. It does not describe response shape, latency, or caching, which leaves a modest gap for a paid endpoint.

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?

Three tight fragments front-load the paid nature and the returned fields before the cost, auth, and billing guarantees. Every sentence contributes information an agent would otherwise have to guess, and nothing is repeated from structured fields.

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?

There is no output schema, so the description compensates by naming the three returned metrics, and it covers cost, chains, auth, and billing behavior. What is missing is any indication of response encoding or error behavior beyond 'failed calls not charged', which would matter for a paid HTTP endpoint.

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 beyond the schema's empty object; baseline 4 applies. The description correctly conveys that no inputs are needed.

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 asset (Apro / AT) and the exact payload — live USD price, 24h change, market-cap rank — so an agent knows what it gets. The leading 'Paid.' plus the price point implicitly separates it from the large family of free buy_coin_* siblings, but no sibling is named outright, which keeps it below 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 context is implied by 'Paid. ... $0.01 USDC on Base or Solana' and 'No account, no API key', which tells the agent what prerequisites are needed before calling. There is no explicit statement of when to choose this over an alternative (e.g., a free quote endpoint for the same asset) or when not to call it.

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