Skip to main content
Glama

SouthPow crypto & market data

buy_coin_MOODENG

Paid. MOODENG/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/MOODENG.

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

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 at all, the description carries the full burden and does a decent job: it discloses the price ($0.01 USDC on Base), the payment rail, the absence of auth requirements, and that failed calls are not charged — a genuinely useful billing-behavior detail. It omits latency/freshness and whether the charge occurs before or after a successful fetch, which is the main remaining gap for a paid tool.

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?

It is dense and front-loaded: 'Paid.' immediately signals the cost model, then the data payload, then payment terms, then the endpoint URL. The telegraphic style is efficient, though the bare URL at the end is slightly unexplained (it is presumably the raw endpoint, not something the agent should call directly).

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 no-parameter, no-output-schema paid price lookup, the description covers cost, payment method, auth requirements, failure billing, data sources and returned fields — essentially everything needed to invoke it correctly. The only missing piece is guidance on choosing this versus the generic crypto price sibling.

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 no parameter semantics to explain and the baseline of 4 applies. The description instead spends its space on output fields and payment mechanics, which is the right allocation.

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?

The description names the exact resource (MOODENG/USD live price) and enumerates the returned fields: last price, 24h open/high/low, % change, 24h and 30d volume. That is enough to distinguish it from the hundreds of sibling buy_coin_* tools, each of which covers a different asset.

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?

It establishes context ('Paid', no account or API key needed, failed calls not charged) which tells the agent it can call this without setup. But it never says when to prefer this over the generic sibling buy_crypto_price, nor does it state any prerequisite such as a funded USDC balance on Base before the call will succeed.

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