Skip to main content
Glama

SouthPow crypto & market data

buy_coin_MANTLE

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/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 calls are paid ($0.01 USDC on Base), that no auth is needed, that failures are not charged, and the upstream sources (Coinbase Exchange with Kraken cross-check). It stops short of rate limits, latency, or failure/error semantics beyond the no-charge rule.

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?

Very compact and front-loaded: what data, at what cost, under what access conditions, at which URL. The telegraphic style ('Paid.', 'No account, no API key.') trades some readability for density but every fragment carries 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?

For a no-param, no-output-schema price tool with no annotations, the description covers the returned fields, the payment model, and auth requirements, which is what an agent needs to call it. Minor gaps remain around error behavior and the response envelope shape.

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 convey; the baseline for a no-arg tool applies. The description correctly signals this by embedding the asset in the endpoint URL rather than implying any arguments.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: returns live MANTLE/USD price with last price, 24h open/high/low, % change, and 24h/30d volume. The asset ticker in the name plus the explicit data set makes it distinguishable from the hundreds of sibling buy_coin_* tools without opening the schema.

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 rather than stated: an agent can infer this is the tool for MANTLE spot pricing. The description gives access conditions ($0.01 USDC on Base, no account or API key, failed calls not charged) but never says when to prefer it over the generic sibling buy_crypto_price or what to do for other assets.

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