Skip to main content
Glama

SouthPow crypto & market data

buy_coin_SYND

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden and does well: it discloses the price ($0.25 USDC on Base), no account or API key required, that failed calls are free, and the underlying data sources and endpoint URL. It stops short of describing response format, latency, or whether the price is cached/stale.

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?

Dense and front-loaded: payment flag first, then the payload, then cost/logistics, then URL. The telegraphic sentence fragments ('Paid.', 'No account, no API key.') are efficient but border on cryptic for an agent unfamiliar with x402-style paid endpoints.

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-output-schema tool, the description enumerates the returned fields and their provenance, which is the key missing structure. It does not state the wire format (JSON shape) or freshness guarantees, a minor gap given the simplicity of the call.

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; baseline 4 applies. The description usefully clarifies that the ticker and quote currency are baked into the endpoint rather than being inputs.

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 specifically that this returns live SYND/USD data: last price, 24h open/high/low, % change, and 24h/30d volume, with named sources (Coinbase Exchange, Kraken cross-check). The resource is unambiguous, though the 'buy_coin_' prefix suggests a trade rather than a paid data read, which the description only implicitly corrects via '$0.25 USDC'.

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 by the SYND/USD scope, and it clearly frames the call as paid with 'Failed calls not charged', which helps an agent decide whether to spend. However, it never says when to prefer this over siblings like buy_crypto_price or the other 300+ buy_coin_* tickers, leaving selection to inference from the name.

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