Skip to main content
Glama

SouthPow crypto & market data

buy_tok_VELVET

Paid. Velvet (VELVET) 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/VELVET.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With zero annotations the description carries the full burden and mostly delivers: it discloses that the call is paid, the exact cost ($0.05 USDC), the accepted payment chains (Base or Solana), that no authentication is required, and that failed calls are not charged. Rate limits and response/pagination behavior are unstated, but the commercial and failure semantics are unusually well covered.

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?

Information-dense but front-loaded: 'Paid.' and the price first, then cost, payment rails, auth, and failure policy. The raw endpoint URL is arguably infrastructure noise for an agent invoking an MCP tool, but every other clause carries decision-relevant information.

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 price lookup, the description supplies the returned fields, the price of the call, how to pay, and the failure-cost policy — enough to invoke it confidently. Only the exact response structure and freshness/latency of the 'live' price are left implicit.

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 no parameters, so the baseline is 4; the description correctly frames this as a parameterless call (token identified by the tool itself, not by input). No additional parameter meaning is needed or expected here.

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 resource (Velvet/VELVET) and the exact payload: live USD price, 24h change, and market-cap rank. It is unambiguous what the tool returns, but it never distinguishes itself from the near-identical sibling buy_coin_VELVET or from the generic buy_crypto_price, so an agent choosing among hundreds of token tools gets no routing signal.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance at all — nothing tells the agent whether to prefer this over buy_coin_VELVET or buy_crypto_price. The 'No account, no API key' line is a prerequisite fact, not usage guidance, and no exclusions or alternatives are mentioned.

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