Skip to main content
Glama

SouthPow crypto & market data

buy_coin_ACS

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

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

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 supplied, the description carries the full burden and does well: it discloses that the call is paid ($0.05 USDC on Base), needs no account or API key, and that failed calls are not charged — all decision-relevant for an autonomous agent. It stops short of describing rate limits, what counts as a 'failed' call (e.g., HTTP error vs. empty payload), or the response shape.

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?

It is a single dense line with the cost marker ('Paid.') front-loaded, followed by the payload, payment mechanics, and endpoint. No filler and every clause conveys a distinct fact an agent needs before spending money.

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 parameterless paid fetch with no output schema and no annotations, the description covers cost, payment rail, auth requirements, failure billing, and the fields returned — nearly everything needed to call it correctly. The only gap is the concrete response format and failure semantics, which the missing output schema leaves unaddressed.

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 empty schema is the complete contract. Baseline 4 applies for a parameterless tool.

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 the exact resource (ACS/USD live price) and enumerates the returned fields: last price, 24h open/high/low, % change, 24h and 30d volume. It also names the data sources (Coinbase Exchange with Kraken cross-check). It does not need to differentiate from the hundreds of buy_coin_* siblings since the ticker is in the name, but it also never states a verb like 'fetch' or 'returns'.

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 only implied: an agent infers it should call this when it needs ACS spot pricing. There is no explicit when-to-use or when-not guidance, and no mention of the generic sibling buy_crypto_price (which could plausibly cover the same need) or of when a cross-check against another source is preferable.

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