Skip to main content
Glama

SouthPow crypto & market data

buy_tok_YGG

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

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

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 supplied, the description carries the full burden and does so well: it discloses that calls are metered ($0.01 USDC), payable on Base or Solana, that no account or API key is needed, and that failed calls are not charged — all behavior an agent can't get from structured fields. It falls short of full marks by omitting latency, rate limits, and what a failure response looks like.

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?

Front-loads the key fact ("Paid") and the asset/payload in the first sentence, then payment and access terms, then the endpoint. Every clause carries distinct information with no redundancy, which is the right shape for a one-shot priced data lookup.

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, output-schema-less price lookup, the description covers what is returned (price, 24h change, market-cap rank), the cost and payment chain, and access requirements. Only failure modes and response shape detail are missing, which is a minor gap at this complexity.

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 there is nothing to disambiguate and the baseline applies. The description correctly doesn't waste words on parameter semantics, though it could have noted that the asset is baked into the endpoint rather than passed as input.

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?

Names a specific asset ("Yield Guild Games (YGG)") and the exact payload ("live USD price, 24h change and market-cap rank"), which is more than a restated tool name. It doesn't state how it relates to the hundreds of sibling buy_coin_*/buy_tok_* price tools, so an agent must infer this is the YGG-specific instance rather than the generic 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?

Usage is only implied: fetch this when you need YGG price data. There is no explicit when-to-use vs. alternative guidance, no mention of the generic buy_crypto_price or other YGG-adjacent tools, and no exclusions. The cost and payment rails are stated, which helps an agent decide whether to spend, but the routing logic is left to inference.

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