Skip to main content
Glama

SouthPow crypto & market data

buy_tok_VENOM

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

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

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 discloses that the call is paid, the price and accepted chains, that no account or API key is needed, that failures are not billed, and the underlying endpoint URL. It stops short of saying how payment is actually settled by the caller or whether there are rate limits or caching behavior.

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 "Paid." so the cost gate is the first thing an agent sees, then packs pricing, auth, billing policy and endpoint into four compact sentences with no filler. The clause grouping is slightly cramped but every sentence carries operational information.

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 no-parameter, no-output-schema price lookup, the description supplies the missing return-value summary (USD price, 24h change, market-cap rank) and the commercial prerequisites an agent needs before invoking. Only the concrete response format and any freshness/latency guarantees are absent.

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 the baseline is 4 and there is nothing for the description to disambiguate. It usefully redirects the reader to the fixed resource and the shape of the returned fields instead of wasting space on nonexistent arguments.

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 exact resource (Venom/VENOM) and enumerates what is returned: live USD price, 24h change and market-cap rank. That is a specific verb-plus-resource statement, but it never explains how it differs from adjacent siblings like buy_crypto_price or a generic coin-price tool, so an agent must infer the distinction from the name.

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?

The description gives decision-relevant cost context ("$0.05 USDC on Base or Solana", "Failed calls not charged"), which implicitly helps an agent weigh whether calling is worth it. However, it never states when to use this tool versus buy_crypto_price or any coin-specific alternative, so routing guidance is only implied.

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