Skip to main content
Glama

SouthPow crypto & market data

buy_tok_RSNDK

Paid. SanDisk Tokenized Stock (Reality) (RSNDK) 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/RSNDK.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/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 disclose genuinely useful behavior: it is a paid call, the price is $0.05 USDC, payment is accepted on Base or Solana, no account or API key is needed, and failed calls are not charged. It does not cover rate limits, latency, data freshness, or error semantics beyond the free-on-failure note.

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?

It is front-loaded with the most important fact ('Paid') and then packs return fields, cost, auth requirements and endpoint into a few dense sentences. The raw URL is the only element of questionable value to an agent, but it is short and does not bloat the text.

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 call with no output schema, the description must supply both the return shape and the commercial terms, and it does both explicitly. Gaps are minor: no mention of freshness/update cadence or what an error response looks like, though 'Failed calls not charged' partially covers failure handling.

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 at the argument level; baseline applies. The description correctly implies no inputs are needed by presenting the ticker as fixed in the endpoint.

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 specific resource (SanDisk Tokenized Stock, ticker RSNDK) and enumerates exactly what the call returns: live USD price, 24h change and market-cap rank. It stops short of an explicit verb and never distinguishes this tool from the close siblings buy_tok_SNDKB and buy_tok_SNDKX, which an agent could easily confuse with it.

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 choose this tool over alternatives, and no guidance on the near-identical SanDisk variants in the sibling list. The payment terms ('$0.05 USDC on Base or Solana', 'Failed calls not charged') describe cost conditions but are not routing 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