Skip to main content
Glama

SouthPow crypto & market data

buy_coin_HOME

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

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

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 present, the description carries the full burden and does well: it discloses the price ($0.01 USDC on Base), that no account or API key is required, that failed calls are not charged, the upstream data sources (Coinbase Exchange with Kraken cross-check), and the endpoint URL. It stops short of describing response shape, latency, or data freshness guarantees.

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?

Front-loaded with 'Paid.' so the cost signal arrives before anything else, then fields, then payment mechanics, then URL — a sensible priority order. It is telegraphic and dense, but nearly every clause carries distinct 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-parameter, no-output-schema tool, the description covers the three things an agent needs: what data comes back, what it costs, and that failure is free. Only the concrete response format and freshness/staleness behavior are left unstated, which is a minor gap given the field list already provided.

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 baseline of 4 applies; there is no ambiguity about what inputs are needed. The description correctly signals this by baking the ticker into the tool rather than exposing an argument.

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?

Names the exact resource (HOME/USD) and enumerates the returned fields — last price, 24h open/high/low, % change, 24h and 30d volume — so an agent knows precisely what it gets. It never explicitly differentiates itself from the overlapping buy_crypto_price sibling or the hundreds of other buy_coin_* entries, relying on the ticker in the name to do that work.

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 description implies usage ('live' pricing, exchange sources) but never states when to pick this over buy_crypto_price or the generic price tools, nor any conditions where a call is wasteful. The cost and no-auth notes give practical context for deciding to call, which lifts it above pure implication.

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