Skip to main content
Glama

SouthPow crypto & market data

buy_tok_AB

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 a lot of work: it discloses paid pricing ($0.05 USDC), accepted chains (Base or Solana), that no account or API key is needed, that failed calls are not charged, and the endpoint URL. That covers cost, auth, and failure policy well, though rate limits and response shape are not addressed.

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?

Six short telegraphic statements, front-loaded with 'Paid' so cost is the first thing the agent sees; nothing is padded. 'AB (AB)' is a redundant restatement and a couple of fragments are terse to the point of being clipped, which costs a point.

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 price lookup, the description supplies the three returned metrics, the price, the payment rails, the auth situation, and the failure-charge policy, which is most of what an agent needs. Remaining gaps are minor: no explicit mention of the response format or freshness/rate-limit behavior.

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 0-param tool applies. The description's only parameter-adjacent value is confirming which asset is priced (AB), which it does.

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?

"AB (AB) price: live USD price, 24h change and market-cap rank" names the resource and the exact fields returned, so an agent knows what it gets without opening anything. It is clearly a single-token price endpoint, but with both buy_tok_AB and buy_coin_AB in the sibling list, the description never explains how the 'tok' family differs from the 'coin' family, leaving a real ambiguity.

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: fetch AB's price data. There is no explicit statement of when to prefer this over buy_coin_AB, buy_crypto_price, or buy_tok_* alternatives, and no exclusions or prerequisites beyond the payment note. An agent can infer the context but gets no routing help.

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