Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ASSET

Paid. REAL (ASSET) 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/ASSET.

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

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 behavioral burden and does well: it discloses that the call is paid, the exact price ($0.05 USDC), accepted chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged. Missing only rate limits and payment-flow mechanics.

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-loaded with the most decision-relevant token ('Paid.') and packed with cost, auth, and endpoint facts in a few short clauses. The 'REAL (ASSET)' phrasing is slightly awkward since ASSET is a placeholder, but nothing is wasteful.

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 paid endpoint with no output schema, the description covers return fields, price, payment chains, auth requirements, billing on failure, and the base URL. Only the mechanics of paying (e.g., how the USDC payment is attached to the request) are left unstated.

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 no parameter semantics to explain; the baseline of 4 applies. The description instead clarifies that the asset is fixed by the tool itself, which removes any ambiguity about missing inputs.

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 and payload: live USD price, 24h change and market-cap rank for ASSET. The tool name carries the asset identity and the description explains what the call returns, so an agent can distinguish it from the many buy_tok_* siblings only by symbol, not by function.

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?

Implied usage is clear (call to get the price of this specific asset), and payment prerequisites are spelled out. However, it never tells the agent when to prefer this over siblings like buy_crypto_price or buy_coin_<SYM>, nor that this tool is bound to a single asset while those may cover others.

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