Skip to main content
Glama

SouthPow crypto & market data

buy_coin_AST

Paid. AST/USD live: last price, 24h open/high/low, % change, 24h and 30d volume (Coinbase Exchange, Kraken cross-check). $0.25 USDC on Base. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/AST.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations exist, so the description carries the full behavioral burden and does well on the commercial side: $0.25 USDC on Base, no account or API key, and failed calls are not charged, plus the concrete endpoint URL. It says nothing about rate limits, latency, or response shape beyond the field list, and the 'Paid.' prefix is terse enough that the actual trigger for a charge is left somewhat implicit.

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 key fact ('Paid.') and then packs data content, price, payment terms, auth requirements and endpoint into a few dense lines with no filler. The telegraphic style is efficient but slightly harder to parse than plain sentences, keeping it off a 5.

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?

With no output schema, the description must describe return values and it does, listing every metric included and the underlying exchanges. Cost, payment rail, auth and failure-charging are all covered. Only cross-source reconciliation behavior (what happens when Coinbase and Kraken disagree) and freshness/latency are missing.

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; there is nothing about inputs the description could usefully add. The URL effectively fixes the resource, which is the closest thing to a parameter here and it is fully specified.

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 (AST/USD live price) and enumerates the returned fields: last price, 24h OHLC, % change, 24h and 30d volume, plus the sources (Coinbase Exchange with Kraken cross-check). That distinguishes it from the hundreds of buy_coin_<TICKER> siblings by ticker. It never uses an explicit verb like 'fetch' or 'retrieve', relying on the field list to convey the action.

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 only implied: an agent can infer this is the AST price source because the description names that pair. There is no statement of when to prefer this over the generic buy_crypto_price sibling or over other AST-related tools, nor any exclusion. The price and no-account terms do help an agent decide whether to spend, which lifts it above a bare 2.

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