Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ANIME

Paid. Animecoin (ANIME) 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/ANIME.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/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 discloses cost ($0.05 USDC), accepted chains (Base or Solana), that no account or API key is needed, and crucially that failed calls are not charged. Only rate limits and any caching/freshness guarantees are unstated.

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-loaded with 'Paid.' and then the payload description, with cost/auth/failure terms packed into short clauses. The raw endpoint URL is the only marginally expendable element, though it aids transparency.

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 lookup with no output schema, the description states what is returned, what it costs, how to pay, and the failure-billing policy — enough for an agent to decide and invoke. Freshness/source latency is the only notable omission.

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 baseline for a no-param tool applies. The ticker is baked into the endpoint, which reinforces that no input is needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names the specific asset (Animecoin/ANIME) and the exact payload returned: live USD price, 24h change and market-cap rank. The verb+resource pairing combined with the ticker makes it trivially distinguishable from the hundreds of sibling buy_tok_* tools.

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?

The asset scope implies when to call it, and 'Paid ... $0.05 USDC' tells the agent there is a cost before invoking. But there is no explicit when-to-use/when-not framing and no routing to generic alternatives such as buy_crypto_price or buy_coin_* for broader or differently-sourced pricing.

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