Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ELF

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/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 it delivers the non-obvious traits: this is a paid, metered call, the exact price, the accepted payment networks, that no authentication is required, and that failures are not billed. It does not cover response shape, data freshness/latency, or what happens if settlement fails mid-call, which keeps it out of the top band.

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?

Four short clauses, front-loaded with 'Paid.' so the cost signal hits first, then the payload, then the payment mechanics, then the endpoint. No sentence is filler and nothing essential is buried.

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 one-shot, no-parameter, no-output-schema price lookup, the description covers the upstream data, price, payment rails, auth requirements, and failure billing, which is everything needed to decide and call. Only the absence of any indication of response format or data recency keeps it below 5.

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 and the schema is empty, so there is nothing to disambiguate; the description correctly avoids inventing arguments. Baseline 4 applies for a parameterless 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?

The description names a specific resource (aelf / ELF) and enumerates exactly what comes back: live USD price, 24h change, market-cap rank. It is far clearer than the dozens of near-identical buy_tok_* siblings, but it never explains how buy_tok_ELF relates to buy_coin_* or buy_crypto_price, so the family boundary is left to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Cost ($0.05 USDC), payment chains (Base or Solana), and the no-account / no-API-key precondition effectively tell an agent it can call this without setup, and 'Failed calls not charged' sets expectations for retry behavior. It stops short of naming an alternative free or generic price tool when the caller only needs a rough quote.

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