Skip to main content
Glama

SouthPow crypto & market data

buy_tok_TKX

Paid. Tokenize Xchange (TKX) 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/TKX.

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

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 does real work: it discloses that the call is paid ($0.01 USDC), names the accepted payment chains, states no account or API key is required, and clarifies that failed calls are not charged. It stops short of describing rate limits, latency, or response shape beyond the listed price fields.

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?

Front-loads the ticker and the returned fields before the billing details, and every sentence carries information. The trailing raw URL is mildly redundant with the tool name but still useful for transparency.

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 price lookup, the description covers what is fetched, what comes back, what it costs, and how payment works. Only the response format (JSON shape, numeric precision) and freshness guarantees are left unstated, which are minor for this class of tool.

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; baseline 4 applies. The description correctly signals a parameterless fixed-symbol endpoint, so an agent knows no arguments are needed.

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 verb and resource ('Tokenize Xchange (TKX) price') plus the exact fields returned: live USD price, 24h change, and market-cap rank. That makes it distinguishable from unrelated siblings like buy_tvl_* or buy_fx_*, but it never explains how it differs from buy_crypto_price or the large buy_coin_* family, so sibling differentiation is only implicit in the ticker.

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 USDC on Base or Solana when you need the TKX spot price. It gives no when-to-use vs when-not guidance and does not name an alternative such as buy_crypto_price, so an agent must infer the choice from the tool name alone.

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