Skip to main content
Glama

SouthPow crypto & market data

buy_coin_DRV

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Since no annotations are present, the description carries the full behavioral burden. It is highly transparent about the data scope (Coinbase/Kraken cross-check), the cost structure ('Paid'), and the safety of invocation ('Failed calls not charged').

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 extremely dense and efficient, successfully front-loading all critical information—what it is, what it measures, the exchanges checked, the cost, and the technical URL—in a single paragraph with zero wasted words.

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?

Given that the tool has no input parameters and no output schema is specified, this description is fully complete. It provides all necessary context for the agent to understand its capability, cost, and technical implementation details.

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 schema provides no parameters, meaning schema coverage is 100%. Therefore, the description merely reinforces the function rather than providing added semantic meaning to required inputs. Baseline score for zero parameters is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description specifies the exact resource (DRV/USD live price) and the specific metrics provided (last price, 24h open/high/low, % change, and 24h/30d volume). This specificity distinguishes it perfectly from other sibling tools by focusing on the asset DRV.

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?

While it doesn't provide a formal 'when-to-use' guide, it sets extremely clear operational guidelines by stating the tool is 'Paid', lists the cost ($0.002 USDC), and ensures the agent knows 'No account, no API key' is required for invocation.

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