Skip to main content
Glama

SouthPow crypto & market data

buy_coin_MET

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

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

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, the description carries the full burden and does well: it discloses that the call is paid ($0.05 USDC on Base), requires no account or API key, and that failed calls are not charged — all critical for an agent deciding whether to spend. It also names the endpoint URL and data sources, though it says nothing about latency, rate limits, or response shape.

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?

Very dense and front-loaded — price scope first, then cost, then access terms, then URL. The telegraphic fragments ('Paid.', 'No account, no API key.') read efficiently, though the opening one-word sentence is slightly awkward and the URL could be a structured field rather than prose.

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, no annotations, and no parameters, the description must supply everything, and it covers what the agent needs: returned fields, sources, cost, payment rail, failure billing, and endpoint. Only return-format details and rate/latency behavior are absent, which is a minor gap for a single-shot paid lookup.

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; baseline 4 applies. The description correctly implies the symbol is baked into the endpoint rather than passed as an argument.

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?

States a specific resource (MET/USD live price) and enumerates exactly what is returned: last price, 24h open/high/low, % change, 24h and 30d volume. The named upstream sources (Coinbase Exchange, Kraken cross-check) further pin down the data, so an agent can distinguish this from the ~300 other buy_coin_* siblings purely by symbol.

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 implied rather than stated: fetch live MET pricing. There is no explicit when-to-use/when-not guidance and no pointer to an alternative (e.g., buy_crypto_price for broader coverage or another sibling for a different asset). The payment and access notes help an agent decide it *can* call, but not when it *should*.

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