Skip to main content
Glama

SouthPow crypto & market data

buy_tok_TRIBE

Paid. Tribe (TRIBE) 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/TRIBE.

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

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 full behavioral burden and does so well: it discloses the paid cost ($0.01 USDC), the accepted payment chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged — a genuinely important billing safeguard. It omits any note on rate limits, freshness/caching of the price, or response shape beyond the field names.

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?

Compact and front-loaded, with the 'Paid' flag and the data payload first, then cost/payment, then trust signals, then the URL. The telegraphic 'Paid.' fragment and the trailing raw URL are slightly awkward but each clause carries information.

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-argument, no-output-schema price endpoint, the definition covers the essentials an agent needs before spending money: what data comes back, what it costs, how to pay, that no auth exists, and that failures are free. Only the returned structure and data freshness are left unspecified.

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 for the description to disambiguate at the argument level. Baseline 4 applies; the description correctly makes clear the asset is fixed by the tool itself rather than passed in.

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?

States a specific resource (Tribe / TRIBE) and enumerates exactly what is returned: live USD price, 24h change, and market-cap rank. An agent can tell this is a single-asset spot price lookup. It does not distinguish itself from the generic buy_crypto_price sibling, which is the only remaining ambiguity.

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: the 'Paid' prefix and the price/cost disclosure signal that this is a per-call purchase, and the fixed symbol means no selection is needed. However, there is no explicit statement of when to pick this instead of buy_crypto_price or the buy_coin_* family, and no guidance on prerequisites.

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