Skip to main content
Glama

SouthPow crypto & market data

buy_tok_VERONA

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

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

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 zero annotations, the description carries the full burden and does well: it discloses that calls are paid ($0.05 USDC on Base or Solana), that no account or API key is needed, and that failed calls are not charged. It stops short of rate limits, latency, or what counts as a failure, which keeps it off a 5.

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?

Six short segments, front-loaded with the payment marker and the payload description, with no filler. It is slightly telegraphic ('Paid.'), and the raw endpoint URL is of limited use to an agent in selecting the tool, but nothing is bloated.

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 tool, it covers purpose, returned fields, cost, payment rails, and failure billing, which is most of what an agent needs. Missing only edge-case behavior such as rate limits or what the response shape looks like on error.

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 no semantics to add beyond the empty schema; the baseline of 4 applies. The description does not waste space restating inputs, 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?

States the specific resource (Verona / VERONA price) and the exact payload returned: live USD price, 24h change, market-cap rank. That is far better than the sibling buy_tok_* tools, which are distinguishable only by name. It does not mention nearby siblings such as buy_crypto_price, so it falls short of 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?

Implies context (fetch this when you need the VERONA price) and the no-account/no-API-key framing hints at when it is convenient. But there is no explicit when-to-use versus alternatives, no statement about when this is preferable to buy_crypto_price or unrelated endpoints, and no prerequisites section 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