Skip to main content
Glama

SouthPow crypto & market data

buy_tok_TREAD

Paid. Tread.fi (TREAD) 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/TREAD.

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

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 burden and does well: it discloses that the call is paid ($0.05 USDC on Base or Solana), that no account or API key is required, that failed calls are not charged, and it gives the endpoint URL. The remaining gap is how payment is actually presented or settled on the call, which an agent must discover elsewhere.

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?

It is front-loaded ('Paid.') and then moves straight into the price fields, cost, prerequisites, and failure policy with essentially no filler. The literal endpoint URL is the only element of questionable value to an agent, though it does support verification.

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-annotation, no-output-schema tool, the description covers what is returned, the price, the auth model, the failure-charge policy, and the endpoint. Only the precise shape of the returned payload and the payment mechanics are left unstated, which are minor for this complexity level.

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, which is the baseline-4 case. The description correctly implies the token is fixed by the tool itself rather than passed in, so there is nothing extra a parameter explanation could add.

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 specific resource (Tread.fi / TREAD) and enumerates exactly what is returned: live USD price, 24h change, and market-cap rank. That is a concrete verb-plus-resource statement. It does not, however, contrast itself with nearby siblings such as buy_crypto_price or buy_coin_* variants, so sibling differentiation is left to the tool name.

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 by the token name and the enumerated data points, and the description adds useful prerequisites ('No account, no API key'). It never states when an agent should pick this over buy_crypto_price or a buy_coin_* endpoint, nor any exclusion, so routing between near-identical siblings is still inference.

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