Skip to main content
Glama

SouthPow crypto & market data

buy_tok_VANA

Paid. Vana (VANA) 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/VANA.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/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, the exact price and accepted chains, that no credentials are needed, and that failed calls are not charged — the refund policy is the kind of detail agents rarely get. It stops short of explaining the payment mechanism (how USDC is actually tendered) or any rate limits.

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 the critical fact ('Paid.') and then delivers cost, data contents, and prerequisites in terse fragments with no filler. The telegraphic style and trailing raw URL cost it a bit of polish, but every clause carries information an agent needs.

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 tool this covers the essentials: what data comes back, what it costs, on which chains, and that failures are free. It is slightly incomplete on the payment handshake and the exact response shape, which matters given the monetary cost of each call.

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 input schema is an empty object with zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies all variability (symbol, chain) is fixed by the tool itself rather than by arguments.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Vana (VANA) price') and enumerates exactly what the payload contains: live USD price, 24h change, and market-cap rank. Against the huge buy_tok_* / buy_coin_* sibling family, the token-specific naming plus the explicit field list makes it unambiguous which symbol this tool covers.

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?

Gives useful invocation context — $0.01 USDC on Base or Solana, no account or API key — but offers no routing advice against alternatives such as buy_crypto_price or buy_tok_* variants, and no guidance on when this is preferable to a generic price endpoint.

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