Skip to main content
Glama

SouthPow crypto & market data

buy_tok_NVDAB

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations supplied, the description carries the full burden and does disclose meaningful operational traits: it is a paid call at $0.05 USDC on Base or Solana, requires no account or API key, and failed calls are not charged. It stops short of stating rate limits, data freshness/latency, or what a failure response looks like, so it is strong but not exhaustive.

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?

The description is a tight block with the payload described first, then price/access terms, then the URL — front-loaded and free of filler. The 'Paid.' fragment is terse to the point of being abrupt, but no sentence is wasted.

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 lookup tool, the description covers what is returned, what it costs, which chains settle payment, the failure billing policy, and the endpoint. The main remaining gap is data freshness — 'live' is unquantified — and expected response shape, which matters given no output schema exists.

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 there is no parameter semantics to explain; baseline 4 applies. The description correctly implies no inputs are needed by giving a fully qualified endpoint URL.

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?

The description names the exact asset (NVIDIA bStocks Tokenized Stock, ticker NVDAB) and enumerates the returned fields: live USD price, 24h change, market-cap rank. That is a specific verb+resource statement. It does not, however, distinguish this endpoint from the closely named siblings buy_tok_NVDA, buy_tok_NVDAON and buy_tok_NVDAX, which an agent could easily confuse.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to call this versus alternatives such as buy_crypto_price or the other NVIDIA-ticker tools. The only conditional content is commercial (price, chains, failure policy), which tells the agent how the call is billed, not when it should be chosen.

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