Skip to main content
Glama

SouthPow crypto & market data

buy_coin_1INCH

Paid. 1INCH/USD live: last price, 24h open/high/low, % change, 24h and 30d volume (Coinbase Exchange, Kraken cross-check). $0.01 USDC on Base. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/1INCH.

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

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, the description carries the full burden and does well: it discloses the cost ($0.01 USDC on Base), the payment chain, that failed calls are not charged, and the underlying data sources (Coinbase Exchange with Kraken cross-check). It omits rate limits, latency, and whether the price is cached or real-time.

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 front-loads the payment flag ('Paid.') and then packs the data payload, price, access terms, and endpoint URL into a few terse clauses. The telegram style is slightly dense but every element (cost, failure policy, sources) carries information an agent needs.

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, the description must convey what comes back, and it lists the returned metrics and their provenance. Only the exact response shape (JSON field names, units, timestamp) is left unstated, which is a minor gap for a simple price 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 the baseline is 4; there is nothing for the description to disambiguate. It correctly documents the fixed asset (1INCH) and quote currency (USD) that would otherwise be implicit.

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 a specific resource and payload: 1INCH/USD last price, 24h open/high/low, % change, and 24h/30d volume, with the URL ending in /v1/price/1INCH. Siblings are same-prefix per-coin tools, so the ticker in the name plus the URL path differentiates it adequately, though no explicit verb (e.g. 'fetch') is used.

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 states access conditions ('No account, no API key', $0.01 USDC on Base), which implicitly tells the agent this is a paid endpoint usable without setup. However, it never says when to prefer this over siblings such as buy_crypto_price or buy_coin_00, nor any when-not-to-use case.

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