Skip to main content
Glama

SouthPow crypto & market data

buy_coin_DEEP

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose meaningful behavior: payment amount and chain, no auth required, and that failed calls are not charged. It omits what a failure looks like, latency, and response/pagination behavior, so the disclosure is useful but incomplete for a paid endpoint.

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 definition is telegraphic but tightly packed: cost is front-loaded as 'Paid.', followed by return fields, pricing, and access terms, with no filler. The fragmentary phrasing costs a little readability but nothing is wasted.

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?

With no output schema and no annotations, the description supplies the return field list, sources, price, auth requirements, and billing policy — enough for an agent to decide and invoke. It stops short of describing the response envelope or failure modes, which is a minor gap for a zero-parameter 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 the baseline is 4; there is no parameter semantics to add. The description correctly implies a no-argument call by listing the fixed asset pair and endpoint URL.

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 (DEEP/USD live price) and enumerates exactly what is returned: last price, 24h open/high/low, % change, 24h and 30d volume. It identifies the data sources (Coinbase Exchange, Kraken cross-check). The verb is only implicit ('Paid.' then a field list), and sibling differentiation relies on the asset name rather than any explicit wording, which keeps it just short of a 5.

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?

It conveys practical conditions — costs $0.01 USDC on Base, no account or API key needed, failed calls not charged — which tells an agent when it is viable to call. However, it never says when to prefer this over alternatives such as the generic buy_crypto_price sibling, nor any exclusions.

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