Skip to main content
Glama

SouthPow crypto & market data

buy_coin_METIS

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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.25 USDC-on-Base cost, that no account or API key is needed, and that failed calls are not charged — the three facts an agent most needs before spending money. It stops short of rate limits, payment mechanics, or what a failed call looks like.

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?

Front-loads 'Paid.' so cost is the first thing seen, then data contents, then price/auth/refund terms, then the URL. Dense and telegraphic with no filler sentences; every clause carries information.

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, no-output-schema endpoint, the description enumerates the returned fields and data provenance, which substitutes well for a schema. Minor gaps remain: response format/encoding and how the USDC payment is actually settled are unstated.

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; the description correctly implies the coin pair is baked into the endpoint rather than passed in. Nothing is left ambiguous about invocation inputs.

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?

States a concrete verb+resource: live METIS/USD price data with the exact field set (last, 24h open/high/low, % change, 24h/30d volume) and named sources. The ticker-scoped name plus the explicit pair makes it distinguishable from the hundreds of sibling buy_coin_<TICKER> tools, though the description never says 'this is the METIS variant of a per-token family'.

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: the coin pair and data fields tell an agent what it returns, and 'No account, no API key' signals it can be called freely. There is no explicit when-to-use statement, no mention of the generic sibling buy_crypto_price as an alternative for multi-asset lookups, and no guidance on caching or repeated calls.

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