Skip to main content
Glama

SouthPow crypto & market data

buy_coin_EDGEX

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/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 well: it discloses the $0.05 USDC-on-Base cost, that no account or API key is required, that failed calls are not charged, and that data is sourced from Coinbase Exchange with a Kraken cross-check. Missing only latency/staleness and response format details, which is a modest gap.

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?

It is front-loaded with 'Paid.' then the data payload, followed by cost, access requirements, and the endpoint URL — a sensible priority order with no filler. It is written in terse fragments rather than full sentences, which is efficient though slightly staccato.

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?

There is no output schema, no annotations, and no parameters, so the description must supply the return shape and commercial terms itself — and it does, listing every returned field and the full payment model. Only operational details like freshness guarantees or error behavior beyond billing are absent.

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 nothing for the description to disambiguate and the baseline of 4 applies. The description instead spends its words on what the parameterless call returns and costs, which is the right allocation.

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 identifies the resource precisely (EDGEX/USD live price feed) and enumerates the exact fields returned: last price, 24h open/high/low, % change, and 24h/30d volume. It does not describe the 'buy' verb beyond noting it is paid, but the coin pair in the name plus the field list make the tool's function unambiguous relative to the many buy_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 Guidelines3/5

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

Usage is only implied: an agent infers it should call this to obtain live EDGEX/USD market data. There is no explicit statement of when to prefer this over generic siblings such as buy_crypto_price, nor any exclusion or alternative named, leaving selection guidance to inference from the coin pair.

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