Skip to main content
Glama

SouthPow crypto & market data

buy_tok_TORN

Paid. Tornado Cash (TORN) 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/TORN.

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

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 load and does well: it flags the tool as paid, states the exact cost ($0.01 USDC on Base or Solana), notes no account or API key is required, and confirms failed calls are not charged. It does not mention rate limits, latency, or whether the payment is per-call or session-based, which 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?

Front-loads 'Paid.' so cost is known before anything else, then gives data scope, pricing detail, and endpoint in short fragments. Every element earns its place, though the pricing/endpoint tail reads as a dense run-on rather than clearly separated lines.

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, the description covers cost, payment rails, auth requirements, failure billing, and the returned fields. The only missing piece is a note on response shape or freshness/caching of the 'live' price, which is minor at this complexity.

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 to disambiguate and the baseline of 4 applies. The description correctly adds no parameter discussion, avoiding noise.

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 exact asset (Tornado Cash / TORN) and enumerates what the call returns: live USD price, 24h change, and market-cap rank. It is unambiguous what the tool does, but it never references the sibling family (the hundreds of buy_tok_* and buy_coin_* tools) so an agent must infer the token-specific scope 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?

Usage is implied by the token-specific name and the data listed, but there is no explicit 'use this instead of buy_crypto_price' or 'this covers TORN only' statement. For an agent choosing among hundreds of near-identical siblings, an explicit routing statement would be valuable.

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