Skip to main content
Glama

SouthPow crypto & market data

buy_tok_TST

Paid. Test (TST) 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/TST.

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

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: it discloses cost ($0.01 USDC), accepted payment rails (Base or Solana), that no credentials are needed, and the billing policy for failures. Missing only return-shape and freshness/latency details, which is what keeps it from a 5.

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?

Roughly three short sentences with the payload description front-loaded, followed by price/access facts. The trailing endpoint URL is the weakest element—useful for debugging but not for tool selection—and the fragment style ("Paid.") is terse but readable.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-param, no-output-schema tool, the description should say what comes back, and it does at a high level (price, 24h change, rank). It omits anything about response format or staleness, so an agent knows what it buys but not quite what it will receive.

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 implies the ticker is fixed by the tool itself rather than passed in.

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 concrete resource (Test/TST price) and enumerates exactly what is returned: live USD price, 24h change, market-cap rank. That is far more specific than the bare tool name, though it never explicitly distinguishes itself from the ~800 sibling buy_tok_/buy_coin_/buy_crypto_price tools beyond 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 only implied by the ticker in the name; there is no statement of when to prefer this over buy_crypto_price or a buy_coin_TST-style sibling. It does add the practically useful conditions (paid, no account or API key, failed calls not charged), which helps an agent decide whether to call at all.

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