Skip to main content
Glama

SouthPow crypto & market data

buy_coin_RAY

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations supplied, the description carries the behavioral burden well: it discloses that calls are paid, the exact $0.002 USDC price, the Base network, the lack of account or API-key requirements, and that failed calls are not charged. It also identifies Coinbase Exchange as the source and Kraken as a cross-check, giving useful provenance context.

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?

The description is compact and information-dense, leading with the paid nature and then covering data scope, provenance, cost, authentication, failure billing, and endpoint. Although written in fragments, every phrase serves invocation or selection and there is no filler.

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 zero-input, fixed-resource price tool, the definition supplies the essential metrics, sources, cost, network, access requirements, failure-charging behavior, and URL. The absence of an output schema is substantially offset by the explicit list of returned market metrics, and no additional parameters or operational prerequisites appear necessary.

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 has no parameters, so the baseline is 4 and there are no undocumented inputs requiring explanation. The fixed RAY endpoint URL reinforces that callers do not need to supply an asset symbol or other options.

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 clearly identifies the resource as live RAY/USD market data and enumerates the available price, change, and volume metrics. It clarifies that the tool retrieves quote data despite the potentially misleading 'buy_coin' name, but it does not explicitly distinguish this fixed-asset tool from buy_crypto_price or other coin siblings.

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

Usage Guidelines4/5

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

The fixed RAY/USD scope, live-data emphasis, and named exchanges provide clear context for when this tool is appropriate. There are no explicit when-not instructions or directions to use buy_crypto_price for other assets or a more general workflow.

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