Skip to main content
Glama

SouthPow crypto & market data

buy_coin_MAMO

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

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

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 ($0.25 USDC on Base), requires no account or API key, is not charged on failure, and that data is sourced from Coinbase Exchange with a Kraken cross-check. Remaining gaps are response shape, latency, and payment-flow mechanics (e.g., how the USDC charge is settled).

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?

Telegraphic and front-loaded: 'Paid.' appears first, followed by what you get, the cost, the auth model, and the endpoint. Nearly every clause earns its place, though the bare URL is marginal for an agent that cannot set it.

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?

There is no output schema, but the description compensates by enumerating the returned fields, and it covers cost, auth, and failure billing for a zero-parameter read tool. What's missing is the response format/envelope and how the payment step is executed, which would matter for an agent that must actually complete a paid call.

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; the baseline applies. The description does usefully note the fixed endpoint URL, which confirms there is nothing to configure.

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 (MAMO/USD) and enumerates exactly what it returns: last price, 24h open/high/low, % change, and 24h/30d volume. The ticker in the tool name plus the explicit field list makes it distinguishable from the hundreds of sibling buy_coin_<TICKER> tools, though it never explicitly states that other tickers live in sibling tools or how it differs from 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 only implied: an agent infers 'call this when you need a live MAMO price snapshot.' The description spends its words on payment mechanics rather than when-to-use guidance, and it never names an alternative (e.g., buy_crypto_price for multi-asset queries) or a when-not-to-use condition.

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