Skip to main content
Glama

SouthPow crypto & market data

buy_tok_VVS

Paid. VVS Finance (VVS) 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/VVS.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 behavioral burden and does so well: it discloses the cost, the accepted payment rails, that auth is not required, and that failed calls are not billed — the billing-on-failure detail is exactly the kind of thing an agent needs before spending money. It stops short of rate limits, latency, or response format.

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?

Front-loads the paid status, then the data returned, then pricing, then the endpoint — each fragment is useful and there is no filler. The URL is the only element an agent may not need, and it is still legitimate operational context.

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, single-value lookup with no output schema, the description covers what is returned, what it costs, how payment works, and where the call goes. Sufficient to invoke confidently; only the response encoding and any rate limit are left unstated.

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 no schema semantics for the description to supplement; baseline is 4. The description correctly signals a parameterless call by making the token identity part of the tool itself.

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?

Names the specific resource (VVS Finance price) and enumerates exactly what comes back: live USD price, 24h change and market-cap rank. Unlike most ticker siblings, which are distinguished only by their name, this one adds explicit output content. The action verb is only implied by the 'price' framing and payment line, which keeps it from a 5.

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?

Establishes clear context for calling it: paid at $0.01 USDC on Base or Solana, no account or API key, failed calls not charged. What is missing is routing guidance — no mention of when a sibling such as buy_crypto_price would be preferred, nor any exclusion or precondition beyond payment.

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