Skip to main content
Glama

SouthPow crypto & market data

buy_tok_VR

Paid. Victoria VR (VR) 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/VR.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does add real value: cost, accepted chains (Base or Solana), no account/API key requirement, and the failure policy (failed calls not charged). It still leaves untested behavior unclear, such as caching/staleness, rate limits, and what an unpaid or expired request returns.

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 what the tool returns before payment mechanics, and every sentence carries new information. The raw endpoint URL is the only element that feels like boilerplate for an agent that invokes tools through the MCP layer rather than by HTTP.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description must state the payload, and it does: price, 24h change, market-cap rank. For a zero-parameter, zero-annotation paid lookup, cost, chains, auth requirements, and failure charges are all covered.

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?

There are zero parameters, so the baseline of 4 applies; nothing is undocumented. The description correctly avoids inventing parameter semantics and instead spends its words on cost and delivery.

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?

The description states a specific resource (Victoria VR / VR) and enumerates exactly what is returned: live USD price, 24h change, and market-cap rank. Against hundreds of near-identical buy_tok_* siblings, the embedded token identity is what lets an agent pick this one without opening the schema.

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?

It establishes the commercial precondition (Paid, $0.01) but never says when to choose this over buy_crypto_price or a sibling token tool, nor what to do when the call fails. The payment context is implied usage guidance rather than explicit when/when-not routing.

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