Skip to main content
Glama

SouthPow crypto & market data

buy_tok_YLDS

Paid. YLDS (YLDS) price: live USD price, 24h change and market-cap rank. $0.05 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/YLDS.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are supplied, so the description carries the entire burden and it does add real context: cost, accepted payment chains, no auth required, and refund-on-failure behavior. It omits other behaviorally relevant facts such as latency, rate limits, caching/refresh cadence of the price, and what a failure response looks like, which matters for a paid endpoint.

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?

Every sentence is load-bearing — purpose, price, payment rails, auth burden, refund policy, endpoint. The only flaws are the redundant 'YLDS (YLDS)' restatement and a raw URL that reads more like developer documentation than agent-facing context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With zero parameters and no output schema, the description does the essential job of enumerating the returned fields (price, 24h change, rank). However, it leaves gaps an agent would care about for a paid call: data freshness/refresh interval and the shape of an error or failed-charge response. It is adequate but not fully complete.

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 imposes no burden and the baseline is 4. The description adds no parameter guidance because none is needed, though it does implicitly confirm the call is fully self-contained (token baked into the endpoint URL).

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?

Uses a specific verb+resource combination ('YLDS price: live USD price, 24h change and market-cap rank') that tells an agent exactly what data comes back. It is distinguishable from generic siblings like buy_crypto_price or the hundreds of other buy_tok_* entries by naming the token, though it never explicitly says 'use this for YLDS rather than buy_crypto_price'.

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 payment terms ('$0.05 USDC on Base or Solana. No account, no API key. Failed calls not charged.') make the preconditions clear and are genuinely useful for deciding whether to call a paid tool. There is no explicit when-to-use/when-not-to-use guidance relative to buy_crypto_price or the buy_stable_ylds sibling, so selection is left implied.

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