Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ABEL

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

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

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 supplied, the description carries the full burden and does well: it discloses the paid model, the exact price and accepted chains for payment, that no credentials are required, and that failed calls are not billed. It omits update frequency/latency and what a partial or errored response looks like, so it stops short of full behavioral disclosure.

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?

It leads with 'Paid.' so the most decision-relevant fact is front-loaded, then gives payload, price, and access terms in short clauses. Every sentence carries information; the trailing endpoint URL is marginally redundant with the tool name but adds transparency, not enough to penalize heavily.

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 quote tool, the description covers purpose, the three return fields, the payment rail and cost, and the failure-charging policy — enough for an agent to invoke it safely. Gaps are minor: data freshness and response units/format are not stated.

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 parameterless tool applies. The description correctly implies no inputs are needed beyond payment/transport setup.

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 a specific resource and payload: 'Abelian (ABEL) price: live USD price, 24h change and market-cap rank.' That is concrete enough for an agent to know exactly what it gets. It does not, however, distinguish itself from the large family of sibling quote tools (buy_coin_*, buy_crypto_price, buy_tok_* variants), so the agent must infer the difference from the ticker in the name alone.

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?

Cost and access conditions are stated ('$0.05 USDC on Base or Solana', 'No account, no API key', 'Failed calls not charged'), which implicitly tells the agent this is a pay-per-call quote it can use without setup. There is no explicit when-to-use or when-not-to-use guidance and no named alternative (e.g., vs buy_coin_ABEL or buy_crypto_price), so routing between siblings is left to inference.

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