Skip to main content
Glama

SouthPow crypto & market data

buy_tok_NVDAX

Paid. NVIDIA xStock (NVDAX) 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/NVDAX.

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

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 does well: it discloses that the call is paid, the exact price and accepted chains, that no auth is needed, that failed calls are not charged, and the underlying endpoint URL. Remaining gaps are minor for a read-only price lookup — nothing about rate limits or error/payment-failure behavior on a successful-call path.

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?

Roughly four short clauses, each earning its place: payload, price/rails, auth posture, billing on failure, endpoint. Cost and constraints are front-loaded after the purpose statement, with no filler.

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 paid price lookup, the description covers what is returned, what it costs, which chains to pay on, that no credentials are needed, and failure billing. It could go one step further on response shape or rate limits, but nothing essential to invoking it correctly is missing.

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; the description correctly implies the asset is fixed by the tool itself (NVDAX) rather than passed in. No parameter meaning is missing because there is nothing to parameterize.

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 payload: "NVIDIA xStock (NVDAX) price: live USD price, 24h change and market-cap rank," which tells an agent exactly what data comes back. It does not differentiate from near-identical siblings such as buy_tok_NVDA, buy_tok_NVDAON, or buy_tok_NVDAB, so an agent must infer the distinction from the tool name alone.

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 by the symbol in the name and the payload description, and payment prerequisites ($0.01 USDC on Base or Solana, no account or API key) are explicit. However, there is no statement of when to prefer this over the plain buy_crypto_price or the other NVDA-family tools, and no exclusions are given.

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