Skip to main content
Glama

SouthPow crypto & market data

buy_tok_STRCX

Paid. Strategy PP Variable xStock (STRCX) 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/STRCX.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 load and does most of it well: it discloses the paid model, the $0.01 USDC cost, the accepted chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged. It stops short of saying how payment is settled or what a successful/failed response looks like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Telegraphic but every clause earns its place: price, output fields, cost, chains, auth, billing policy, endpoint. Front-loaded with the paid status and the resource, no filler.

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 no-param, no-output-schema price lookup, the description covers enough: it enumerates the returned fields and the commercial/technical prerequisites. Missing is the response envelope (JSON shape, error signaling) and pagination-free confirmation, but the essentials for correct invocation are present.

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?

Zero-parameter tool, so baseline is 4. The description correctly signals there is nothing to configure and adds value by stating the fixed cost and settlement chains instead of parameter meaning.

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?

States a specific resource ('Strategy PP Variable xStock (STRCX)') and names the actual returned data (live USD price, 24h change, market-cap rank), so the agent knows exactly what it gets. The 'buy_' prefix and STRCX suffix distinguish it from the hundreds of sibling buy_tok_* entries by argument rather than by prose, but the description never explicitly says how to pick among them.

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 pay-to-call framing implies this is the tool for STRCX pricing, but there is no explicit when-to-use/when-not guidance relative to buy_crypto_price or the other buy_tok_* siblings. Usefulness depends on the agent inferring the token-suffix convention.

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