Skip to main content
Glama

SouthPow crypto & market data

buy_coin_CTSI

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

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

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 supplied, the description carries the full behavioral burden and does well: it discloses the paid model and exact price, that no account or API key is needed, that failed calls are not charged, and where the data comes from. The main residual ambiguity is that the name 'buy_coin_CTSI' could be misread as executing a purchase, and the description never explicitly says this is a read-only price lookup; it also omits rate limits and response format.

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?

Front-loading 'Paid.' is exactly right, and the remaining clauses each carry distinct facts (fields, sources, price, auth, failure policy). It is dense to the point of telegram style, and the trailing bare URL has no label indicating whether it is the endpoint or documentation, which costs a bit of clarity.

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 annotations and no output schema, the description covers nearly everything an agent needs: what data comes back, the venue sources, cost, authentication requirements, and billing on failure. Only the concrete response shape/units (e.g., numeric USD, timestamp, staleness) are left unspecified.

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?

There are zero parameters, so the baseline is 4. The description adds the endpoint URL (https://southpow.media/v1/price/CTSI), which is extra context beyond an empty schema, and there is nothing parameter-level left undocumented.

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 the exact resource and scope: live CTSI/USD data with an explicit field list (last price, 24h open/high/low, % change, 24h and 30d volume) and named sources (Coinbase Exchange, Kraken cross-check). Combined with the ticker-specific tool name, an agent can tell exactly which asset this covers and what it returns, versus the hundreds of sibling buy_coin_<TICKER> tools.

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: an agent infers it should call this when it needs CTSI spot data. The cost statement ('$0.25 USDC on Base', 'Failed calls not charged') is genuinely useful decision input, but there is no explicit when-to-use/when-not guidance and no named alternative (e.g., the generic buy_crypto_price sibling) for broader price needs.

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