Skip to main content
Glama

SouthPow crypto & market data

buy_tok_US

Paid. Talus (US) 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/US.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations at all, the description carries the full behavioral burden and does a solid job: it discloses the monetary cost, accepted payment chains, absence of authentication requirements, and the important billing nuance that failed calls are not charged. It omits how payment is actually settled (pre-funded wallet vs per-call signature) and whether results are cached or real-time, which are the remaining behavioral gaps.

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?

The definition is a tight telegraphic block with no wasted sentences, and the most decision-relevant fact ('Paid') is front-loaded. The choppy fragment style and the trailing raw URL slightly reduce readability compared with a structured sentence flow, but nothing is redundant.

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 paid data endpoint with no output schema and no annotations, the description covers what matters: the exact data fields returned, the price, the payment rails, the absence of auth, the refund policy, and the underlying URL. An agent has everything needed to decide whether to call it and to anticipate the response.

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 the baseline of 4 applies; there is nothing for the description to clarify beyond the schema. The symbol is baked into the endpoint URL, which the description exposes, confirming no inputs are required.

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 a specific resource (Talus/USD price) and enumerates exactly what the payload contains: live USD price, 24h change, and market-cap rank. It is clear what the tool returns, but it does not differentiate itself from the hundreds of near-identical siblings (buy_coin_US, buy_crypto_price), so an agent must infer the tok/coin distinction from the name alone.

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?

Purchase conditions are spelled out (paid, $0.05 USDC, Base or Solana, no account or API key, failures not charged), which tells the agent how to transact. However, there is no guidance on when to choose this endpoint over a sibling price tool, nor any exclusion such as 'use buy_coin_US instead for spot coin data' — the agent is left to infer selection from the tool 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