Skip to main content
Glama

SouthPow crypto & market data

buy_coin_MDT

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations supplied, the description carries the disclosure burden and does well: it declares the tool is paid at $0.25 USDC on Base, that no credentials are required, that failed calls are not charged, and which exchanges back the numbers. The remaining gaps are return format and any rate limit or retry behavior.

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.' and then the payload contents, cost, access conditions and URL, with almost no filler. The heavily telegraphic fragment style ('Paid.', '$0.25 USDC on Base.') is efficient but slightly clipped, requiring the reader to assemble the payment story.

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 tool with no output schema and no annotations, the description covers what data comes back, provenance, cost, and access requirements, which is nearly everything needed to call it. The main omission is how the payment is actually settled and what the response shape looks like.

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; the baseline of 4 applies. The note that no account or API key is needed adds minor value about invocation prerequisites rather than parameter meaning.

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 names the exact resource (MDT/USD), the specific fields returned (last price, 24h open/high/low, % change, 24h and 30d volume), and the data sources (Coinbase Exchange with Kraken cross-check). It also implicitly disambiguates the 'buy_coin_' prefix: this is a paid price feed, not a trading action, which is exactly what an agent needs to know against hundreds of ticker 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?

Prerequisites (paid, no account, no API key, failed calls free) are stated, which tells the agent it can call this without setup. However, there is no explicit when-to-use or when-not guidance and no reference to an alternative such as buy_crypto_price for broader or cheaper coverage, so the routing decision is left to inference.

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