Skip to main content
Glama

SouthPow crypto & market data

buy_tok_AUTO

Paid. Hastra AUTO (AUTO) 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/AUTO.

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

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 that the call is paid ($0.01 USDC), the accepted payment rails (Base or Solana), that no account or API key is required, that failed calls are not charged, and the endpoint URL. It omits rate limits, latency, and the exact response shape, which keeps it short of a 5.

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?

Two dense sentences with the paid nature, returned fields, price, and access constraints front-loaded; nothing is padding. The telegraphic fragment style ('Paid.') is slightly cryptic but reads efficiently and every clause earns its place.

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 lookup, the description supplies the returned fields, cost, payment method, auth requirements, and failure billing policy — enough for an agent to decide and invoke correctly. Only the concrete response format and rate limits are left unspecified, which is minor at this complexity.

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 the baseline is 4. The description correctly implies nothing is needed beyond the call itself, and the fixed URL reinforces that no arguments are supplied.

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?

States a specific resource (Hastra AUTO / AUTO token price) and exactly what it returns: live USD price, 24h change and market-cap rank. The ticker in the name plus the explicit field list makes it distinguishable from the hundreds of sibling buy_tok_* tools without opening the schema.

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 is implied by the resource (call this when you need the AUTO token price), but there is no explicit when-to-use or when-not-to-use guidance, and no pointer to alternatives such as buy_crypto_price or buy_coin_AUTO that might serve overlapping needs. The payment/auth lines give context but not selection guidance.

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