Skip to main content
Glama

SouthPow crypto & market data

buy_coin_SUP

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

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

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 well: it discloses the pay-per-call model, payment asset/chain, no-auth requirement, that failed calls are not charged, and the upstream data sources (Coinbase Exchange with Kraken cross-check). It omits rate limits, latency, and caching behavior, 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?

Front-loaded with the cost signal, then data contents, then payment mechanics, then endpoint URL — a sensible priority order with no filler. The telegraphic fragment style is dense but readable; a slightly more explicit subject for the first sentence would help.

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?

No output schema exists, so the description must describe returns and it does enumerate the fields plus their source. What remains missing is the actual response shape/field names and error semantics beyond the no-charge guarantee, but for a zero-parameter price lookup this is close to sufficient.

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 schema is trivially complete (100% coverage). Baseline 4 applies; the description correctly avoids inventing parameter discussion.

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 the exact resource (SUP/USD live price) and enumerates what is returned: last price, 24h open/high/low, % change, and 24h/30d volume. It does not explicitly contrast itself with the generic sibling buy_crypto_price or explain the SUP ticker mapping, but the per-ticker naming makes the scope unambiguous.

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?

Leads with "Paid" and specifies the cost ($0.10 USDC on Base) and that no account or API key is needed, which is useful spend-side guidance. However, it never says when to pick this over the generic buy_crypto_price tool or what to do if the price feed is stale, so the when-to-use decision is only implied.

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