Skip to main content
Glama

SouthPow crypto & market data

buy_coin_JTO

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/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 behavioral burden and does so well: it discloses the cost and payment rail, that no auth is required, that failed calls are not billed, and that data is sourced from Coinbase Exchange with a Kraken cross-check. It does not state response latency, rate limits, or what an error/failure looks like, which keeps it below a 5.

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 is front-loaded with 'Paid.' — the single most decision-relevant fact — followed by payload contents, price, access requirements, and endpoint, in a dense telegraphic style with no filler. The raw URL at the end is mildly extraneous but harmless and occasionally useful for verification.

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?

There is no output schema, so the description must cover return values, and it does by enumerating every field returned plus their provenance. It never states the wire format (JSON envelope, units, timestamp field), which is the only meaningful gap for a zero-arg data-fetch tool.

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 schema is trivially complete and the baseline applies. The description correctly adds no parameter discussion and instead pins the ticker (JTO) as fixed scope, which is the right use of the space.

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 resource (JTO/USD live price) and enumerates what is returned: last price, 24h open/high/low, % change, 24h and 30d volume. It is unambiguous what the tool does, though it never contrasts itself with generic siblings such as buy_crypto_price; differentiation rests on the ticker in the name rather than on the text.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear operating context: 'Paid', '$0.25 USDC on Base', 'No account, no API key', 'Failed calls not charged' — all of which materially inform when and how an agent should call it. It stops short of explicit exclusions, e.g. when to prefer buy_crypto_price or the non-ticker-pinned alternative, so no alternatives are named.

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