Skip to main content
Glama

SouthPow crypto & market data

buy_tok_VATRENI

Paid. Croatian Football Federation Token (VATRENI) 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/VATRENI.

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

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, the description carries the full burden and does well: it declares the price ($0.01 USDC), accepted chains (Base or Solana), the absence of auth requirements, and the billing policy on failures. It stops short of describing latency, caching/freshness guarantees beyond 'live', or the error/response shape, so it is strong 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?

Front-loads the payment flag, then the data payload, then cost/chain/auth/failure terms in short declarative fragments — no filler. The telegraphic style is dense but readable; a little more sentence structure would cost nothing.

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 covers what is sold, what is returned, what it costs, how to pay, and the failure policy. The main residual gap is the response format/schema, which an agent must discover by calling, but that is a modest omission for a tool this simple.

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 nothing for the description to disambiguate; the baseline for a parameterless tool applies. The description correctly implies no inputs are needed by stating no account or API key is required.

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 (Croatian Football Federation Token / VATRENI) and the specific payload — live USD price, 24h change, market-cap rank — so an agent knows precisely what it gets back. It does not explicitly differentiate itself from lookalike siblings such as buy_crypto_price or other buy_tok_* entries, which is why it lands at 4 rather than 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?

It gives acquisition context (paid, no account, no API key, failed calls not charged) which implicitly tells the agent this is a pay-per-call data purchase. However there is no explicit when-to-use versus alternatives guidance, e.g. whether to prefer buy_crypto_price or a category-level tool for broader market data.

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