Skip to main content
Glama

SouthPow crypto & market data

buy_tok_XVS

Paid. Venus (XVS) 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/XVS.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses the commercial traits well: $0.05 USDC on Base or Solana, no account or API key required, and failed calls are not charged. What it omits is equally important for a paid call — rate limits, expected latency, retry semantics, and response format are all unstated, so an agent cannot judge cost or failure risk beyond price.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with 'Paid.' so the cost gate is the first thing the agent sees. Each subsequent clause (data returned, price and payment rails, billing on failure, endpoint) adds distinct information with no filler.

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?

With no input parameters, no annotations, and no output schema, the description must stand entirely on its own, and it does cover what data comes back plus cost and access terms. It still leaves the agent guessing about response shape, latency, and rate limits for a paid call, which is a meaningful gap given the absent structured metadata.

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, which sets the baseline at 4; there is nothing for the description to disambiguate. The inclusion of the endpoint URL is a small extra detail rather than a parameter clarification, which is appropriate 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 specific asset (Venus/XVS) and enumerates exactly what the call returns: live USD price, 24h change, and market-cap rank. That is a concrete verb-plus-resource statement an agent can act on. It does not, however, differentiate itself from near-identical siblings such as buy_crypto_price or the large buy_coin_* family, so the agent must infer the distinction.

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 statement of when to pick this tool over buy_crypto_price or buy_coin_* equivalents, despite hundreds of closely related siblings. The access terms (no account, no API key, failed calls not charged) describe how to use it, not when to choose it. No exclusions or alternatives are given.

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