Skip to main content
Glama

SouthPow crypto & market data

buy_tok_TIG

Paid. The Innovation Game (TIG) 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/TIG.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it declares the tool is paid, the exact price ($0.05 USDC), accepted payment chains (Base or Solana), that no account or API key is needed, and the billing semantics 'Failed calls not charged'. Those are exactly the facts an agent needs before deciding to spend money on behalf of a user.

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?

Three tight sentences plus a URL, front-loaded with the 'Paid.' flag so cost is known before anything else. Every sentence carries distinct information (purpose/payload, price, payment rails, auth, failure billing) with no filler.

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 purchase-and-fetch tool with no annotations and no output schema, the description covers cost, payment, auth, failure billing, and the fields returned — enough to call it correctly. Minor gaps remain: no indication of data freshness/latency beyond 'live', and no guidance on the buy_tok_* vs buy_coin_* family split.

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 no parameter meaning to add; the baseline of 4 applies. The description correctly signals the no-input nature implicitly by specifying a fixed endpoint URL for a single asset.

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 the specific asset (The Innovation Game / TIG) and the exact payload returned (live USD price, 24h change, market-cap rank), which distinguishes it from the hundreds of other buy_tok_* siblings. It does not explain how buy_tok_TIG differs from the parallel buy_coin_* family, so an agent still has to guess which family to use for a token quote.

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 by 'price: live USD price, 24h change and market-cap rank' — quote a spot price for TIG — but there are no explicit when-to-use or when-not statements and no named alternative (e.g., a generic buy_crypto_price tool or the buy_coin_TIG equivalent). With such a crowded sibling namespace, an explicit routing sentence would have real value.

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