Skip to main content
Glama

SouthPow crypto & market data

buy_coin_MORPHO

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

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

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 supplied, the description carries the full burden and does well: it declares the cost ($0.05 USDC on Base), the payment chain, that no account or API key is needed, that failed calls are not charged, and which upstream sources feed the data (Coinbase Exchange with Kraken cross-check). What is missing is the payment mechanism (e.g. x402 flow) and any statement on latency or rate limits for repeated paid calls.

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: cost and asset come first, then the payload, then the access terms, then the endpoint. The telegraphic fragment style ('Paid.', 'No account, no API key.') is efficient but slightly abrupt, and the raw URL is arguably redundant if the tool is invoked via MCP rather than HTTP.

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 annotations and no output schema, the description must describe return content, and it does so by enumerating fields and data provenance. It does not specify the serialization (JSON keys, timestamp field, numeric formatting) or freshness/latency of the quote, which are the remaining gaps for a paid price-feed.

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 per the baseline this dimension starts at 4. The description correctly adds no parameter narrative and instead spends its words on what the fixed call returns, which is the right allocation for a null-argument tool.

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 names the exact asset pair (MORPHO/USD) and enumerates the returned data points (last price, 24h OHLC, % change, 24h/30d volume), so an agent knows precisely what it fetches. Sibling differentiation is only implicit via the ticker suffix shared by hundreds of buy_coin_* tools; there is no explicit 'use this for MORPHO, use X for other tickers' statement, and the generic buy_crypto_price sibling is not addressed.

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?

It gives useful context (paid, no account, no API key, failures not charged) that helps an agent decide whether it can call at all. However, it never states when to pick this over the sibling buy_crypto_price or other buy_coin_* endpoints, and there are no prerequisites or exclusion conditions beyond the implicit ticker match.

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