Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ELG

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

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

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 supplied, the description carries the full burden and does meaningfully well: it discloses that the call is paid, the price and accepted chains, the absence of auth requirements, and that failed calls are not charged. It stops short of explaining how payment is actually settled per invocation or what a failure response looks like, which keeps it out of 5 territory.

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?

Front-loaded with the paywall marker and the asset, then the returned fields, then cost and access terms, then the endpoint. Every clause carries information, though the raw URL is close to redundant with the tool name and the fragment style reads as compressed marketing rather than 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?

No output schema exists, so the description is responsible for the return shape, and it does name the three headline values (price, 24h change, market-cap rank). For a zero-parameter paid lookup this is nearly complete; only the finer shape of the response and the payment handshake are unstated.

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 and the baseline of 4 applies. The description correctly implies a parameterless single-asset call rather than suggesting any filtering inputs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: purchase of the Escoin (ELG) price feed, with the exact payload named (live USD price, 24h change, market-cap rank). Against hundreds of sibling buy_tok_* tools, the asset is named explicitly in both the title line and the endpoint, so an agent can select it without opening the schema.

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?

The payment terms ($0.05 USDC on Base or Solana, no account, no API key, failed calls uncharged) tell the agent what using it costs and requires, which is real usage context. However, it never says when to pick this over the sibling generic price tools such as buy_crypto_price or buy_coin_* equivalents, so routing still depends on the tool name alone.

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