Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ABEY

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

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

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 a good job: it discloses that the call is paid ($0.01 USDC on Base or Solana), that no account or API key is required, that failed calls are not charged, and it gives the literal endpoint URL. That is meaningful behavioral context an agent needs before spending money. It stops short of stating rate limits, latency, or the response shape/schema, hence a 4 rather than 5.

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?

Front-loaded with 'Paid.' so cost is seen first, then one sentence of payload description, then payment/auth/failure terms, then the URL. Every sentence carries information an agent would otherwise have to discover by trial. Nothing is padded or restated.

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-param paid lookup with no output schema, the description covers what is returned, what it costs, on which chains, that no credential is needed, and that failures are free — enough to call it confidently. The absence of a documented response shape or freshness/latency expectation is the remaining gap.

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 no parameter meaning to add and the baseline is 4. The description reinforces this by baking the asset (ABEY) directly into the endpoint path rather than exposing it as an argument.

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 resource (Abey / ABEY) and the exact payload fields (live USD price, 24h change, market-cap rank), so an agent knows precisely what data comes back. It does not distinguish itself from sibling price tools such as buy_crypto_price or the buy_coin_* family, which is the only thing keeping it from a 5.

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 described payload — call this when you need ABEY spot price data. There is no explicit when-to-use vs. alternatives guidance, no mention of when a fresh call is warranted versus cached/sibling endpoints, and no exclusions. Given the large family of near-identical siblings, this gap matters more than it would elsewhere.

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