Skip to main content
Glama

SouthPow crypto & market data

buy_coin_JASMY

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

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

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 provided, the description carries the full burden and does well: it discloses the pricing model, the exact cost and chain, the absence of authentication requirements, the no-charge-on-failure policy, and the upstream data sources (Coinbase Exchange with a Kraken cross-check). The main omission is response shape and latency/refresh cadence, which matter for a live-price endpoint. This is materially more behavioral disclosure than most paid-endpoint definitions offer.

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?

The most important fact for an agent — that this is a paid call — is the very first token, followed immediately by what data is returned, then price, then auth constraints, then the endpoint. Every clause carries distinct information and there is no filler. The telegraphic style suits machine consumption better than prose would.

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-annotation, no-output-schema endpoint, the definition covers what an agent needs before spending money: what it gets, what it costs, what credentials it does not need, and that failures are free. The remaining gap is the per-call latency and data freshness, which an agent budgeting a paid call would reasonably want. Nothing essential is missing.

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 (empty object schema, no required fields), so the baseline of 4 applies. The description correctly requires no argument explanation and instead spends its words on cost and coverage. Nothing about invocation is left ambiguous.

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 and dataset: JASMY/USD last price, 24h OHLC, percent change, and 24h/30d volume. That is a specific resource with a clearly enumerated payload, so an agent knows precisely what it retrieves. It loses a point only because the action verb is implied by the name ('buy_coin_') rather than stated, and the differentiation from sibling buy_coin_* tools comes purely from the asset mentioned.

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?

The description supplies decision-relevant context: it is a paid call, costs $0.05 USDC on Base, needs no account or API key, and failures are not charged. What it never says is when to prefer this over siblings such as buy_crypto_price or the other buy_coin_* entries, nor what the free/paid tradeoff is. Usage is strongly implied (call this when you need JASMY spot data) but never contrasted with an alternative.

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