Skip to main content
Glama

SouthPow crypto & market data

buy_coin_SWELL

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

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

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 provided, the description carries the burden and does well: it discloses cost ($0.01 USDC on Base), payment chain, that no credentials are needed, that failed calls are not charged, and that data is sourced from Coinbase Exchange with a Kraken cross-check. It omits rate limits, latency, and whether the response is JSON, which keeps it short of 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.

Conciseness5/5

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

Two dense sentences with no filler: the paid marker and asset pair lead, the return fields follow, then cost/auth/billing terms, then the URL. Every clause carries information an agent needs before invoking.

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 and no annotations exist, so the description must convey everything, and it covers what fields come back, where the data originates, the price, and the auth model. It stops short only on response format and data freshness, which an agent paying per call would want.

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 meaning to add; the description correctly supplies only endpoint and return-field context. Baseline for a zero-parameter tool applies.

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 (SWELL/USD live price) and enumerates exactly what is returned: last price, 24h open/high/low, % change, and 24h/30d volume. The ticker in the tool name plus the explicit pair makes it distinguishable from the ~350 buy_coin_<TICKER> siblings, though it never explicitly says 'this is the SWELL variant, not the generic price tool'.

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?

It states preconditions for calling (paid, $0.01 USDC on Base, no account or API key) but gives no guidance on when to choose this over the sibling buy_crypto_price or any alternative. Usage is implied by the ticker rather than stated.

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