Skip to main content
Glama

SouthPow crypto & market data

buy_coin_AMP

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

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

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 supplied, the description carries the burden and does well: it discloses that the call is paid, the exact price and payment chain ($0.10 USDC on Base), that no credentials are needed, that failures are not charged, and the upstream sources (Coinbase Exchange with Kraken cross-check). Missing only rate-limit or latency behavior, which is a modest gap for a fixed-price data call.

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?

Seven short fragments, front-loaded with the most decision-relevant fact ('Paid') and then the payload, cost, access terms, and endpoint. Every sentence earns its place, though the raw URL is the least essential element for selection.

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 zero-parameter, no-annotation tool with no output schema, the description covers payload fields, cost, payment rail, auth requirements, failure billing, and data provenance — essentially everything needed to call it correctly. Only the concrete response shape and freshness/timestamp semantics are left unspecified.

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 nothing for the description to disambiguate; the call is fully determined by the tool name. Baseline 4 applies since no parameter meaning is needed.

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?

The description names a specific resource and scope: live AMP/USD pricing, and enumerates exactly which data points are returned (last price, 24h open/high/low, % change, 24h and 30d volume). The token pair in the description makes it trivially distinguishable from the hundreds of sibling per-coin tools.

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 clearly establishes prerequisites and cost ('No account, no API key', '$0.10 USDC on Base', 'Failed calls not charged'), which tells the agent it can call without auth setup. However, it never states when to prefer this over the generic buy_crypto_price sibling or when not to use it, so usage selection 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