Skip to main content
Glama

SouthPow crypto & market data

buy_coin_GROVE

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

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

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?

No annotations are supplied, so the description carries the full burden, and it discloses the key traits: paid cost and currency, no authentication required, failure not billed, and the upstream data sources with a Kraken cross-check. It does not cover latency, rate limits, or the exact response shape, but the payment and auth profile — the highest-risk unknowns — are covered.

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 three dense sentences with no filler: payment status front-loaded as 'Paid,' then the data payload, then cost/auth/billing terms and endpoint. Slightly telegraphic, but every clause carries factual value for the caller.

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 single-symbol quote tool with no output schema, the description supplies the returned fields, payment terms, auth requirements, billing-on-failure policy, and data provenance. The only real gap is the precise response format and any rate/latency limits, which are minor for this complexity.

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 is 4. The description still earns its place by enumerating the returned data fields (last price, OHLC, % change, 24h/30d volume), which compensates for the absence of an output schema.

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 specific resource and scope: 'GROVE/USD live: last price, 24h open/high/low, % change, 24h and 30d volume.' It is unambiguous which asset and which data points are returned. There is no explicit verb beyond 'live,' and differentiation from the hundreds of sibling buy_coin_* tools rests solely on the GROVE symbol and the source list, but the intent is still clear.

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 states the commercial terms ($0.01 USDC on Base, no account/API key, failed calls not charged) which implicitly tells the agent this is a paid, no-setup call. It never states when to prefer this over alternatives such as buy_crypto_price or a different buy_coin_* sibling, so selection guidance is only implied by the symbol in 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