Skip to main content
Glama

SouthPow crypto & market data

buy_coin_MEGA

Paid. MEGA/USD live: last price, 24h open/high/low, % change, 24h and 30d volume (Coinbase Exchange, Kraken cross-check). $0.01 USDC on Base. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/MEGA.

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

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 well: it discloses that this is a paid call ($0.01 USDC on Base), requires no account or API key, and that failed calls are not charged. It omits return-value format, units, latency, and any rate limits, which leaves a modest gap for a zero-parameter paid endpoint.

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?

Roughly forty-five words, front-loaded with the payment flag and the ticker, then the returned metrics, then pricing/access constraints. Every clause carries information an agent needs before spending money, 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-param, no-output-schema, no-annotation tool, the description covers cost, access requirements, billing on failure, data provenance, and the returned fields — which effectively substitutes for the missing output schema. The remaining gap is the shape/precision of the returned values and routing guidance versus buy_crypto_price.

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 of 4 applies; the description correctly does not waste words restating an empty schema.

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 exact resource and payload: MEGA/USD live price with 24h open/high/low, % change, and 24h/30d volume. The ticker in the tool name plus the explicit field list makes it identifiable among the many buy_coin_* siblings. It stops short of 5 because it never contrasts itself with non-ticker siblings like buy_crypto_price.

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 payload listed — an agent can infer it should call this when it needs MEGA spot data. However, there is no explicit when-to-use statement, no mention of when to prefer buy_crypto_price or another sibling, and no guidance on caching or repeated polling despite the per-call charge.

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