Skip to main content
Glama

SouthPow crypto & market data

buy_tok_GVNR

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

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

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 burden and mostly delivers: it discloses that the call is paid, the exact cost ($0.01 USDC), the accepted chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged. Those are exactly the behaviors an agent needs to decide whether a call is viable. It stops short of rate limits, latency/data freshness, and response shape.

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-loaded with the decisive constraint ('Paid.'), then payload, then price/rails, then auth and failure policy, then the endpoint URL. Every clause carries distinct information and nothing is repeated; minor redundancy in 'GVNR (GVNR)' is the ticker-and-name convention, not padding.

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?

With no output schema and no parameters, the description must describe return content, and it does: USD price, 24h change, market-cap rank. Cost, payment rail, auth requirement, and failure billing are also covered. Gaps are secondary: no data-freshness or update cadence, and no indication of response structure or units beyond 'USD'.

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, which is the baseline-4 case; there is nothing parameter-wise for the description to clarify. The description correctly avoids inventing parameters such as a symbol or currency argument, consistent with the empty schema.

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 and the exact payload: "GVNR (GVNR) price: live USD price, 24h change and market-cap rank." That is far more specific than the tool name alone. It does not explicitly say 'this covers only the GVNR token, use the other buy_tok_* entries for other assets', but the embedded symbol plus the naming convention makes the scope unambiguous in practice.

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 only implied by the symbol: an agent can infer 'call this when the user wants GVNR price data.' There is no explicit when-to-use or when-not-to-use statement, and no pointer to an alternative such as buy_crypto_price for a general multi-asset quote. The payment terms are stated, but that is a precondition, not selection 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