Skip to main content
Glama

SouthPow crypto & market data

buy_tok_SNDKX

Paid. Sandisk Corporation xStock (SNDKX) 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/SNDKX.

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

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 supplied, the description carries the full burden and does a solid job: it discloses the cost, the accepted payment chains, that no account or API key is needed, and that failures are not billed — all non-obvious traits an agent must know before spending money. It omits rate limits, latency, and the response format/error behavior, which is the remaining gap.

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?

Four short fragments, front-loaded with the asset and payload, then cost, then access terms, then the endpoint. Every clause carries information (price, fields, price-per-call, chains, auth, billing policy, URL). Slightly telegraphic, but nothing 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 paid lookup with no output schema, the description covers the essentials: what asset, what fields come back, what it costs, how to pay, and that failures are free. Only error conditions and rate limits are left unstated, which is a minor omission given the tool's simplicity.

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 nothing for the description to disambiguate; baseline is 4. The ticker is baked into the tool name and restated in the description, so an agent cannot accidentally parameterize it wrongly.

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 a specific asset (Sandisk Corporation xStock, ticker SNDKX) and the exact data returned: live USD price, 24h change, and market-cap rank. An agent knows precisely what this call yields. It does not, however, distinguish itself from near-identical siblings such as buy_tok_SNDKB or buy_tok_RSNDK, which likely cover related Sandisk instruments.

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 establishes the commercial context ('Paid', '$0.01 USDC on Base or Solana', 'No account, no API key') which implicitly tells an agent this is a usable, low-friction paid lookup, and 'Failed calls not charged' reduces risk of calling it. There is no explicit statement of when to prefer this over sibling ticker tools or over a general price tool, so selection guidance is implied rather than stated.

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