Skip to main content
Glama

SouthPow crypto & market data

buy_coin_AGLD

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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 behavioral burden and does substantial work: it discloses that the call is paid, the exact price, the payment chain, that no credentials are needed, that failures are not charged, and which upstream sources (Coinbase Exchange with Kraken cross-check) back the numbers. What is missing is how the $0.01 payment is actually executed and settled given zero input parameters, plus any rate limits.

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?

Roughly 35 words, telegraphic and front-loaded with the cost flag so the agent sees the paid nature first. The included URL is arguably redundant given the tool already targets that endpoint, and the 'Paid.' fragment is terse to the point of being slightly cryptic.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-param, no-output-schema tool, it does cover what data comes back and what it costs. The real gap is mechanism: a paid tool with no parameters leaves the agent guessing how payment authorization happens and whether a first call fails for lack of funds, which matters for correct invocation of a paid endpoint.

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 the schema has nothing to explain and the baseline of 4 applies. The description correctly does not invent parameter discussion and instead spends its words on cost and data content.

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 asset pair (AGLD/USD) and enumerates the fields returned: last price, 24h open/high/low, % change, 24h and 30d volume. The ticker in the tool name plus the explicit pair distinguishes it from the hundreds of buy_coin_* siblings without needing to open any schema. It stops short of a full verb+resource sentence (the leading 'Paid.' fragment is a cost note, not a purpose statement).

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 gives preconditions for calling (costs $0.01 USDC on Base, no account or API key, failed calls not charged), which is useful context. But it never says when to prefer this over sibling price tools like buy_crypto_price or buy_coin_00, and it offers no exclusions or guidance on freshness/caching.

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