Skip to main content
Glama

SouthPow crypto & market data

buy_coin_GRT

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Since there are no annotations, the description carries the entire burden and performs exceptionally well. It transparently discloses that the call is paid, the cost ($0.05), the payment method (USDC on Base), the lack of credential requirements, and the data sources (Coinbase/Kraken).

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?

The description is densely packed with crucial information—data metrics, cost, and sources—in a concise format. While slightly breathless due to the sheer volume of necessary details, every piece of information is highly relevant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a specific, paid API tool with no input parameters, the description is comprehensive. It identifies the resource, the data points provided, the transaction costs, the payment environment, and provides the actual URL for the operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

As the input schema contains zero parameters, the description must fulfill the entire informational role. It provides all necessary context for the tool's operation, including the specific coin pair (GRT/USD) and the operational details, making it maximally effective for a parameter-less tool.

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 tool is specifically dedicated to providing live price data for GRT/USD. The combination of the unique coin identifier and the listed metrics (price, volume, change) clearly defines its purpose. Although the name suggests 'buy' rather than 'get info', the content clarifies its function as a data feed.

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 usage is implied by the existence of the tool within a massive coin-specific suite. It lacks explicit instructions comparing it against generic tools like 'buy_crypto_price' or 'fetch_fact,' but its specificity serves as functional guidance.

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