Skip to main content
Glama

SouthPow crypto & market data

buy_tok_NVDAON

Paid. NVIDIA (Ondo Tokenized Stock) (NVDAON) 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/NVDAON.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/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 substantial work: it discloses the exact price ($0.05 USDC), accepted chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged — a genuinely useful billing-behavior disclosure. It stops short of rate limits, latency, or what a failure response looks like.

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-loads the paid status, then the data returned, then cost/auth/failure terms, then the endpoint. Every clause carries distinct operational information and there is 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, no-output-schema tool, the definition covers what is returned (price, 24h change, rank), what it costs, where to pay, and how failures are billed. Remaining gaps — response shape and rate limits — are minor at this complexity level.

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. The description correctly conveys that no inputs are required by emphasizing 'No account, no API key', leaving nothing for an agent to supply or misconfigure.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States the exact resource (NVIDIA Ondo Tokenized Stock, ticker NVDAON) and the precise payload returned: live USD price, 24h change and market-cap rank. The parenthetical '(Ondo Tokenized Stock)' disambiguates it from look-alike siblings such as buy_tok_NVDA, buy_tok_NVDAX and buy_tok_NVDAB.

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: an agent can infer 'call this when you need the NVDAON price'. There is no explicit when-to-use versus buy_crypto_price or buy_tok_NVDA, and no statement of when not to use it. The payment/access notes describe conditions of invocation rather than 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