Skip to main content
Glama

SouthPow crypto & market data

buy_coin_YB

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

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

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 burden and does well: it discloses that the call is paid, the exact price ($0.01 USDC on Base), that no account or API key is required, and that failed calls are not charged. That billing-failure policy is exactly the kind of context an agent needs before spending money. Rate limits and data refresh cadence are not mentioned.

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?

The description is a compact block that leads with the most decision-relevant fact ('Paid.'), then the data returned, then cost and auth terms. Every clause carries information, though the trailing bare URL is somewhat abrupt and the opening 'Paid.' is telegraphic rather than a full sentence.

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, but the description enumerates the returned fields (price, OHLC, % change, 24h/30d volume), which effectively documents the response envelope. For a zero-parameter paid endpoint, the remaining omission is data freshness or update frequency, which an agent quoting live prices would want.

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 and there is nothing for the description to clarify about inputs. The listed URL is a minor extra detail but does not substitute for parameter documentation. No meaning is lost because there are no arguments to interpret.

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 and payload: 'YB/USD live: last price, 24h open/high/low, % change, 24h and 30d volume', with sources (Coinbase Exchange, Kraken cross-check). That is far more specific than the bare name buy_coin_YB, which misleadingly suggests a purchase rather than a price-data fetch. It does not explain how it relates to siblings like buy_crypto_price or the other buy_coin_* entries, which is the only real gap.

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 only implied by the asset in the name and the data listed; there is no explicit statement of when to pick this over buy_crypto_price or the generic coin tools. The '$0.01 USDC on Base' cost line does implicitly tell an agent this is a paid call worth using only when YB pricing is actually needed. No exclusions or preconditions are spelled out.

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