Skip to main content
Glama

SouthPow crypto & market data

buy_tok_GAME

Paid. GameBuild (GAME) 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/GAME.

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

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, the description carries the behavioral burden and does so well for the payment dimension: it discloses cost ($0.01 USDC), accepted rails (Base or Solana), no account/API-key requirement, and that failed calls are not charged — a genuinely important detail for a paid tool. It omits freshness/caching behavior and any rate limits, which keeps it from 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Six short fragments, front-loaded with the paid status and the data delivered, then cost, then access constraints, then the endpoint. Nothing is redundant and the most decision-relevant facts (paid, what you get, how much) come first.

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-output-schema tool this covers the essentials: what data comes back (price, 24h change, market-cap rank), what it costs, how to pay, and that failures are free. The main remaining gap is the response format/shape and data freshness, which an agent would otherwise have to discover by calling it.

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; there are no arguments whose meaning the description needs to clarify. The description correctly avoids inventing parameter semantics and instead spends its words on cost and returned fields.

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 a specific resource (GameBuild / GAME) and states exactly what is returned: live USD price, 24h change and market-cap rank. It is clearly distinguishable from the many per-token siblings by naming the token, but it never explicitly contrasts itself with generic siblings such as buy_crypto_price, so it stops short of full sibling differentiation.

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 implied: pay $0.01 to get GAME price data, no account or key needed. There is no explicit when-to-use or when-not-to-use guidance, and no pointer to an alternative (e.g. a multi-token or free price tool) for agents that need something broader.

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