Skip to main content
Glama

SouthPow crypto & market data

buy_tok_TPT

Paid. TokenPocket Token (TPT) 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/TPT.

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

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?

No annotations are supplied, so the description carries the full burden and does a solid job: it discloses the paid nature, the exact cost and payment chains, that no account or API key is needed, and that failed calls are not charged — the last point materially reduces the agent's risk in retrying. It stops short of stating latency, rate limits, or whether the price is sourced on-chain vs aggregated.

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 paid flag, then the resource and payload in one sentence, then commercial terms, then the endpoint. Very little waste. The bare URL at the end is of marginal use to an agent and the telegraphic '$0.05 USDC on Base or Solana' is terse, but neither costs the reader much.

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 lookup tool this covers what matters: what is returned, what it costs, what credentials are not needed, and the failure-billing rule. It would be complete at 5 if it named the source/refresh cadence of the price or pointed to the sibling that covers other tickers.

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 and the baseline of 4 applies. The description correctly implies no input is required by framing the call as a fixed lookup for a single hard-coded token.

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 (TokenPocket Token, TPT) and exactly what data is returned: live USD price, 24h change, and market-cap rank. Clear enough to select without opening a schema, but it never distinguishes itself from the large buy_coin_* / buy_crypto_price family of siblings that plausibly serve the same purpose for a different ticker set.

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: if you want TPT price data, call this. The description does give commercial context ('Paid', '$0.05 USDC on Base or Solana', 'No account, no API key', 'Failed calls not charged') which helps an agent decide whether it can afford to call, but there is no explicit when-to-use / when-not, and no routing away from buy_coin_* or buy_crypto_price alternatives.

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