Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ELON

Paid. Dogelon Mars (ELON) 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/ELON.

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

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 that the call is paid, the exact price ($0.05 USDC), the accepted payment chains (Base or Solana), that no account or API key is required, and that failed calls are not charged. It stops short of covering latency, rate limits, or response shape, so it is strong but not exhaustive.

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?

The content is front-loaded and dense: payload first, then payment terms, then refund policy, then endpoint URL. It is telegraphic rather than smoothly written, but every clause (price, chains, no key, no charge on failure) earns its place and nothing is padded.

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 paid endpoint, the definition supplies what an agent needs: what is returned, what it costs, how to pay, and the failure-charging policy. The absence of a described response structure is acceptable here, though a hint about the returned JSON fields would close the last 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 nothing for the description to disambiguate; baseline 4 applies. Nothing in the text misleads about inputs, and the fixed URL makes the addressability of the specific asset explicit.

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: 'Dogelon Mars (ELON) price: live USD price, 24h change and market-cap rank', so an agent knows exactly what data is returned. It does not, however, differentiate itself from the large sibling set of price tools (buy_coin_*, buy_crypto_price), leaving the agent to infer that this is the ELON-specific variant.

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 asset name; there is no explicit 'use this when…' or 'use buy_crypto_price instead for…' routing statement. The purchasing hints ('No account, no API key', 'Failed calls not charged') help an agent decide whether to commit, but not when to pick this tool over alternatives.

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