Skip to main content
Glama

SouthPow crypto & market data

buy_coin_ME

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

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

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, the description carries the full burden and does a lot of it: paid, price ($0.002 USDC on Base), no auth required, no charge on failure, and the upstream sources (Coinbase Exchange with Kraken cross-check). It does not state data freshness/latency or rate limits, which are the remaining behavioral facts an agent would want before spending money repeatedly.

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?

Extremely tight and front-loaded: payment and data content come first, cost and auth in the middle, URL last. The telegraphic fragment style ('Paid. ME/USD live:') reads a bit like an ad but wastes nothing. Every sentence carries a distinct fact.

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 and no annotations, yet the description enumerates the returned fields and the data sources, so an agent knows what it gets for its $0.002. Missing freshness/latency and any response-format hint (JSON vs text) keeps it from a 5, but it is otherwise complete for a zero-parameter paid data tool.

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 the baseline is 4; there is nothing for the description to disambiguate. The description correctly avoids inventing parameters and instead spends its words on the return fields.

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?

States a specific resource (ME/USD live price) and enumerates exactly what data comes back: last price, 24h OHLC, % change, 24h and 30d volume. The ticker-specific name plus the 'ME/USD' framing makes it distinguishable from the hundreds of sibling per-coin tools. It stops just short of an explicit statement of how it differs from generic 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?

The description makes clear this is a paid per-call endpoint in a family of coin tools, and the 'No account, no API key' line signals it is callable without setup. However, it gives no guidance on when to pick this over buy_crypto_price or another token's tool, nor any note about caching or repeated-call cost tradeoffs that would matter for a paid call.

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