Skip to main content
Glama

SouthPow crypto & market data

buy_coin_APT

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

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

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, the exact price and payment chain ($0.10 USDC on Base), that no auth is needed, that failed calls are not charged, and the upstream data sources (Coinbase Exchange with Kraken cross-check). Gaps remain on rate limits, latency/caching of the price feed, and the response serialization format.

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?

'Paid.' is front-loaded so the cost signal lands first, followed by the data payload, payment terms, and URL in a tight single paragraph with no filler. Every clause carries operational 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 zero-param paid endpoint with no output schema, the description covers cost, payment asset/chain, auth requirements, failure billing, data sources, and the exact fields returned. The only meaningful omission is the response shape/encoding, which an agent would want before parsing results.

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, which is the baseline-4 case; there is nothing to document. The description adds no parameter confusion and implicitly confirms that the ticker and field set are fixed.

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 a concrete resource (APT/USD live price) and enumerates exactly the fields returned: last price, 24h open/high/low, % change, 24h and 30d volume. It's immediately distinguishable from siblings because the ticker is baked into the tool name and description (each sibling covers a different coin). It stops short of 5 because it never names an alternative path (e.g. buy_crypto_price) or restates the APT-only scope as an explicit exclusion.

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?

Provides decision-relevant context — '$0.10 USDC on Base', 'No account, no API key', 'Failed calls not charged' — which tells an agent the cost and prerequisites of calling it. However, there is no explicit when-to-use/when-not guidance relative to siblings like buy_crypto_price or buy_pm_crypto, so the agent must infer that this is the APT-specific paid path.

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