Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ANDY

Paid. ANDY ETH (ANDY) 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/ANDY.

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

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, the description carries the full burden and does well: it discloses the price ($0.05 USDC), the two accepted payment chains (Base, Solana), that no account or API key is needed, and that failed calls are not charged. It omits freshness/latency of the price and any retry or rate-limit behavior.

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 short sentences: what you get, what it costs and how to pay, then the endpoint. Front-loaded with the payload and no filler.

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 simple fixed-query paid endpoint with no parameters and no output schema, the description covers the returned fields (USD price, 24h change, market-cap rank), payment rails, auth requirement, and billing on failure. Only price freshness and response shape are left implicit.

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 description correctly implies a fixed, single-token query with no arguments.

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?

States a concrete resource and result: 'ANDY ETH (ANDY) price: live USD price, 24h change and market-cap rank.' Naming the specific token distinguishes it from the many buy_tok_* and buy_coin_* siblings, though it never contrasts itself with the near-duplicate buy_coin_ANDY or buy_crypto_price.

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 payment framing ('Paid... $0.05 USDC on Base or Solana') implies these are pay-per-call data purchases, but there is no explicit when-to-use or when-not-to-use statement and no routing to alternatives such as the free-form buy_crypto_price or buy_coin_ANDY.

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