Skip to main content
Glama

SouthPow crypto & market data

buy_coin_DRIFT

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does a fair job: it discloses that calls are paid ($0.25 USDC on Base), require no account or API key, are not charged on failure, and pull from Coinbase Exchange with a Kraken cross-check. It does not cover latency, rate limits, or what a failed call returns, which are meaningful gaps for a paid, unauthenticated endpoint.

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?

Front-loaded with the critical qualifier 'Paid.', followed by data fields, pricing/auth terms, and the endpoint URL in a compact telegraphic style. Every clause carries information an agent needs; nothing is redundant.

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 what data comes back, where it comes from, what it costs, and that failure is free. It stops short of describing the response shape or units, but the field enumeration largely compensates given the simplicity of the tool.

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 no parameter semantics to explain and the baseline of 4 applies. The description instead spends its words on the fixed asset and response fields, which is the right allocation for a no-arg call.

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 (DRIFT/USD spot data) and enumerates exactly what is returned: last price, 24h open/high/low, % change, and 24h/30d volume. It is clearly a single-asset price feed, distinguishable from generic siblings like buy_crypto_price, though it never explicitly states the 'this is the DRIFT ticker' routing rule that the name itself carries.

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?

Usage is implied by the asset name and the listed data fields, but there is no explicit when-to-use vs when-not guidance and no reference to the sibling alternatives (e.g. buy_crypto_price for aggregate lookups). The cost and payment requirement give useful selection context, yet the agent must infer that this tool is only for DRIFT.

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