Skip to main content
Glama

SouthPow crypto & market data

buy_tok_EURSPKCC

Paid. Spiko Digital Assets Cash & Carry Fund - Euro Share Class (EURSPKCC) 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/EURSPKCC.

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

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, the description carries the full burden and does well: it discloses the paid model, the exact price ($0.01 USDC on Base or Solana), that no account or API key is needed, and that failed calls are not charged. It omits rate limits, latency, and failure-mode detail, but the commercial and auth behavior an agent most needs before spending money is stated explicitly.

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?

Front-loaded with 'Paid.' so cost is the first thing the agent sees, then asset, payload, price, access conditions, and URL. It is dense and largely waste-free, though the terse fragment style ('No account, no API key.') reads as a list rather than prose.

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 price lookup with no output schema and no annotations, the description covers what is returned (price, 24h change, market-cap rank), the cost and payment rails, auth requirements, and the endpoint. Only the exact response shape and error behavior are unstated, which is a minor gap at this complexity.

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 implies no inputs are needed by fixing the asset in the name and quoting the endpoint URL, leaving nothing for the agent to supply.

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 asset (Spiko Digital Assets Cash & Carry Fund, Euro Share Class, EURSPKCC) and the exact payload: live USD price, 24h change, market-cap rank. That is a clear verb-plus-resource statement an agent can match to a price request, though it never explicitly contrasts itself with the many sibling buy_tok_* / buy_coin_* tools.

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 by 'price: live USD price, 24h change and market-cap rank' — an agent can infer this is for quoting EURSPKCC, but there is no statement of when to prefer it over sibling price tools or category endpoints. Payment context ('Paid', '$0.01 USDC') is given, which helps the agent decide whether to spend, but not which tool to pick.

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