Skip to main content
Glama

SouthPow crypto & market data

buy_tok_STKRI

Paid. Striker (STKRI) 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/STKRI.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

With zero annotations the description carries the full burden and does well: it discloses that the call is paid, the exact price ($0.01 USDC), accepted payment rails (Base or Solana), that no account or API key is needed, and that failed calls are not charged. It falls short of describing response format or data freshness/caching behaviour.

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?

Very short and front-loaded: payment status first, then payload, then cost and access conditions. Sentences are telegraphic fragments rather than prose, which costs a little readability but wastes nothing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter, output-schema-less price lookup, the definition covers everything needed to invoke it correctly: what asset, what data comes back, what it costs, how to pay, and that failures are free. Missing response-shape detail is acceptable given the explicit field list.

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 no parameters and the schema is empty, so there is nothing the description needs to disambiguate. The description compensates for the empty schema by stating the asset is fixed at STKRI, making clear the agent cannot request other tokens through this call.

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 the exact resource (Striker / STKRI) and enumerates the fields returned: live USD price, 24h change, and market-cap rank. The verb is implicit rather than stated, and no sibling is named, but the token-specific naming in a family of per-token buy_tok_* tools makes the scope unambiguous.

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?

No explicit when-to-use or when-not-to-use guidance, and no routing advice against adjacent alternatives such as buy_crypto_price or the buy_coin_* family that may cover the same asset. The only decision-relevant context is that the call is paid, which tells the agent to weigh cost but not when this tool is the right choice.

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