Skip to main content
Glama

SouthPow crypto & market data

buy_coin_SUSHI

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

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

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 well: it discloses that the call is paid ($0.002 USDC on Base), requires no account or API key, that failed calls are not charged, and which exchanges back the data. Remaining gaps are the payment mechanism (how the USDC is actually settled) and any rate limits, but the core commercial and access behavior is unusually well disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads 'Paid.' so cost is seen before anything else, then packs the payload, the price, the access terms, and the URL into a few dense fragments with no filler. Every clause carries decision-relevant information.

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, so the description compensates by enumerating the returned fields and their provenance. What is missing is the response shape/format (JSON keys, units, timestamp semantics for 'live'), which an agent would need to consume the result programmatically.

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?

There are zero input parameters, so the baseline is 4. The description adds that all scoping is baked into the endpoint (single ticker, single URL), meaning the agent needs to supply nothing — which is useful confirmation rather than redundant detail.

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 states a concrete verb-and-resource: retrieve live SUSHI/USD price data, enumerating exactly what is returned (last price, 24h OHLC, % change, 24h and 30d volume) and the sources (Coinbase Exchange, Kraken cross-check). It implicitly differentiates from the hundreds of sibling ticker tools, though notably the tool name 'buy_coin_SUSHI' suggests purchasing a coin while the description makes clear this is a read-only price feed, which the description corrects rather than the name.

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 implied: use this when you need live SUSHI/USD quotes. It does not name alternatives such as buy_crypto_price (a generic price tool) or explain when a cross-checked spot feed is preferable to other market-data siblings. The cost note ('$0.002 USDC') gives a decision-relevant condition but no explicit when-not 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