Skip to main content
Glama

SouthPow crypto & market data

buy_tok_VCRED

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does a decent job: it discloses that calls are paid, the exact price and accepted payment chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged. It also names the return fields, which substitutes for the absent output schema. It leaves out rate limits, latency, and what counts as a 'failed' call, so it is informative but not exhaustive.

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?

One compact sentence chain, front-loaded with the critical fact ('Paid') before the value proposition and payment mechanics. Every clause carries information. Minor waste in the redundant 'VCRED (VCRED)' and the raw URL, which is more for humans than agents.

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 paid endpoint, the description covers the essentials an agent needs: what data comes back, what it costs, what credentials are unnecessary, and where the request goes. The only real gap is payment mechanics -- how the $0.05 is actually settled (e.g., x402 flow) -- which an agent attempting to invoke it would want to know.

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 there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly implies the symbol is hard-coded into the endpoint URL rather than passed as an argument.

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?

States a specific resource (VCRED price) and the exact payload returned: live USD price, 24h change and market-cap rank. An agent can tell what it gets without opening the schema. It does not, however, differentiate itself from the hundreds of buy_tok_* siblings or from buy_crypto_price, so the reader must infer that the symbol baked into the tool name is the whole distinction.

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?

Usage is implied rather than stated: call this when you need the VCRED token price. There is no explicit 'use buy_crypto_price instead for a general quote' routing nor any exclusion conditions. The payment terms ($0.05 USDC, no key, failed calls free) do help an agent decide whether to spend, but that is cost guidance, not use guidance.

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