Skip to main content
Glama

SouthPow crypto & market data

buy_coin_XLM

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/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 most of it: it discloses the charge ($0.01 USDC on Base), that no account or API key is required, that failed calls are not billed, and where the data comes from. What is missing is the payment mechanism (how USDC is actually settled/authorized) and any rate-limit or latency note, which matters for a monetized call.

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?

Front-loaded with the single most decision-relevant fact ('Paid'), then payload fields, then cost and access terms, then the URL. Telegraphic rather than wasteful — every clause carries a fact an agent needs to decide or to call.

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?

No output schema exists, and the description compensates by enumerating the returned fields and their granularity (24h vs 30d volume). It also covers billing and access conditions. The only gap is operational: how payment on Base is executed at call time and what a failure response looks like.

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 and the baseline of 4 applies. The description does not add spurious parameter talk, keeping the zero-arg calling contract clean.

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?

Names the exact resource (XLM/USD live price) plus the field set returned: last price, 24h open/high/low, % change, 24h and 30d volume. It also names sources (Coinbase Exchange with Kraken cross-check) and the endpoint URL, which removes all ambiguity versus the hundreds of sibling ticker 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?

The leading 'Paid' plus the '$0.01 USDC on Base' price establishes the cost context, implicitly telling an agent when this is worth calling. However, it never names an alternative such as buy_crypto_price or says when not to use this (e.g. when a free or bulk price source suffices), so selection among siblings is left to inference.

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