Skip to main content
Glama

SouthPow crypto & market data

buy_tok_AEVO

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

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

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 behavioral burden and does a solid job: it discloses that the call is paid ($0.05 USDC), the accepted payment chains (Base or Solana), that no account or API key is needed, that failed calls are not charged, and the underlying URL. It omits rate limits, data freshness/latency, and what a failure or payment rejection looks like.

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?

Telegraphic and front-loaded: the paid flag and the returned fields come first, then pricing, then access terms, then the endpoint. Every sentence carries information, though the fragments ('Paid.', the bare URL) read as compressed rather than polished prose.

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 covers what is returned (price, 24h change, rank) and what it costs to invoke, which is the information an agent needs before spending money. Only freshness and error behavior are missing, and those are minor at this complexity level.

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 beyond confirming the symbol is fixed to AEVO, which the text does implicitly. Baseline 4 applies for a zero-parameter tool.

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?

States a specific resource (Aevo/AEVO) and an explicit payload: live USD price, 24h change and market-cap rank. An agent can tell what data it gets without opening anything. It does not, however, distinguish itself from generic siblings such as buy_crypto_price or the parallel buy_coin_* family that presumably return similar data for other assets.

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 by the token name — an agent infers 'call this when you want the AEVO price.' There is no explicit when-to-use, when-not-to-use, or pointer to an alternative like buy_crypto_price for arbitrary symbols, so routing between the near-identical token siblings is left entirely to name matching.

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