Skip to main content
Glama

SouthPow crypto & market data

buy_coin_MLN

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

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

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 present, the description carries the full burden and does well: it discloses the $0.05 USDC-on-Base charge, that no account or API key is required, and that failed calls are not billed — all non-obvious operational facts. It stops short of rate limits, caching/latency, and what a failure looks like, so it is strong but not complete.

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 compact and front-loaded, leading with 'Paid.' and the data payload before pricing, auth, and URL. The telegraphic fragment style (dollar price, source list, raw URL) is efficient but slightly terse for an agent parsing cost and failure semantics.

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, the description compensates by enumerating the returned fields and naming the price sources. Payment, auth, billing-on-failure, and the endpoint URL are all covered; only the response envelope shape and rate/latency expectations are absent, which are minor for a single fixed quote.

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 (empty object schema, 100% coverage), so the baseline is 4 and the description correctly spends no words on parameters.

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 a concrete resource (MLN/USD) and enumerates the exact data returned: last price, 24h open/high/low, % change, 24h and 30d volume. It also names the upstream sources (Coinbase Exchange with Kraken cross-check), so an agent can distinguish this feed from generic siblings like buy_crypto_price without opening the schema.

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?

Cost, payment rail, and the no-account/no-API-key condition implicitly tell the agent this is a paid, credential-free quote endpoint, and 'Failed calls not charged' helps with retry decisions. However, there is no explicit when-to-use versus alternatives (buy_crypto_price, other ticker variants) and no statement of when not to use it.

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