Skip to main content
Glama

SouthPow crypto & market data

buy_coin_GRVT

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

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

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 supplied, the description carries the full burden and does well: it discloses the paid cost ($0.10 USDC on Base), that no account or API key is needed, that failed calls are not charged, the underlying data sources (Coinbase Exchange with Kraken cross-check), and the exact endpoint URL. It does not cover rate limits, latency, or freshness of the quote, which keeps it short of a 5.

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?

Everything is packed into a few telegraphic fragments with the most decision-relevant fact ('Paid.') front-loaded, followed by payload, cost, access terms, and endpoint. Nothing is redundant and no sentence is filler.

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-purpose data tool with no output schema, the description enumerates the returned fields, names the price pair, discloses cost and access requirements, and gives the URL — essentially everything an agent needs to call it. Only the absence of a 'prefer buy_crypto_price for general queries' style routing note and output format details leaves a small gap.

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; the ticker is fixed by the tool itself. Baseline 4 applies for a parameterless tool, and the description correctly avoids inventing or implying any 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?

The description states a concrete resource and scope: live GRVT/USD price with last price, 24h open/high/low, percent change, and 24h/30d volume. That is far more specific than the tool name 'buy_coin_GRVT', which alone would suggest a trading action rather than a data lookup. It does not explicitly differentiate itself from buy_crypto_price, which is the main remaining gap.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance and no mention of the alternative buy_crypto_price endpoint. The only usage-adjacent statements ('Paid', 'No account, no API key', 'Failed calls not charged') describe access mechanics rather than selecting this tool over a sibling.

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