Skip to main content
Glama

SouthPow crypto & market data

buy_tok_TBK

Paid. TronBank (TBK) 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/TBK.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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 burden and does well on the commercial side: it discloses the $0.05 USDC cost, that payment works on Base or Solana, that no account or API key is required, that failed calls are not charged, and it gives the endpoint URL. It does not say how fresh the price is, whether responses are cached, or what error/settlement behavior looks like beyond the refund note.

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?

Six short fragments, with the most decision-critical fact ('Paid.') front-loaded, followed by what you get and what it costs. Nothing is redundant, though the telegraphic style trades some readability for density.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 paid lookup, the description covers purpose, returned fields, price, payment rails, authentication requirements and failure billing. An agent has everything needed to decide whether to call it and what the $0.05 outlay buys.

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 and the schema is empty, so there is nothing for the description to disambiguate. The baseline of 4 applies; the description correctly avoids inventing parameter details that do not exist.

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 the resource (TronBank/TBK) and the exact payload it returns: live USD price, 24h change and market-cap rank. That is enough to distinguish it from the hundreds of sibling buy_* endpoints by asset. It stops short of a 5 because the action verb is only implied ('price:' rather than an explicit fetch/get statement).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to choose this over adjacent tools such as buy_coin_* or buy_crypto_price, nor any prerequisite or exclusion beyond the payment mechanics. An agent is left to infer selection purely from the token symbol in the name.

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