Skip to main content
Glama

SouthPow crypto & market data

buy_coin_MOG

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

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

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 so well for a paid endpoint: it discloses the price ($0.25 USDC on Base), that no account or API key is required, that failed calls are not charged, and that quotes come from Coinbase Exchange with a Kraken cross-check. Rate limits and the response envelope are not covered, keeping it below a 5.

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?

Very compact and front-loaded — cost, data contents, payment, auth, billing policy, source URL. The telegraphic phrasing ('Paid.' as a standalone fragment, then a colon list) is dense but readable, and no sentence is filler. A clearer lead verb would improve it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter, paid, single-asset price endpoint with no output schema, the description covers everything an agent needs before calling: what data comes back, what it costs, on which chain and asset, that no credentials are needed, and that failures are free. Only the exact response shape is unspecified, which is a minor 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 and the schema is empty, so there is nothing for the description to disambiguate. Baseline of 4 applies; the description correctly avoids inventing parameter-like configuration options.

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 resource and enumerates exactly what it returns: 'MOG/USD live: last price, 24h open/high/low, % change, 24h and 30d volume'. That is specific enough for an agent to know this is a price-fetch endpoint rather than a trade endpoint despite the 'buy_coin_' prefix. It does not explicitly contrast itself with the hundreds of sibling token tools or with buy_crypto_price, so it falls short of a 5.

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: the word 'live' and the listed fields suggest it is for obtaining current MOG market data, and '$0.25 USDC on Base' hints at the cost tradeoff. There is no explicit statement of when to prefer this over buy_crypto_price or the generic buy_coin_* siblings, and no when-not-to-use guidance.

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