Skip to main content
Glama

SouthPow crypto & market data

buy_tok_SRX

Paid. StorX (SRX) 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/SRX.

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

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 at all, the description carries the full behavioral load and does well: it discloses that the call is paid, the exact price and payment chains, that no credentials are required, and that failed calls are not charged. That failure-billing guarantee is genuinely useful context an agent cannot get from structured fields. Remaining gaps are latency and rate limiting.

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?

Roughly four short clauses plus a URL, with the 'Paid.' flag and the payload summary front-loaded. It is telegraphic rather than prose, but every sentence carries distinct information; only the bare URL line borders on filling space.

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, zero-annotation, no-output-schema tool, the description covers the essentials: what data comes back, what it costs, how to pay, and that auth is unnecessary. An agent knows enough to call it, though the return shape (field names, units) is only loosely sketched.

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 the asset is fixed by the tool itself (SRX), so there is nothing for an 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 a specific resource and payload: 'StorX (SRX) price: live USD price, 24h change and market-cap rank', with an explicit verb in the name (buy) and a concrete endpoint. It is clear what the tool returns, but it never distinguishes itself from adjacent price siblings such as buy_coin_* or buy_crypto_price, so an agent must infer that this is the per-asset variant.

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?

It establishes preconditions ('No account, no API key') and cost ('$0.05 USDC on Base or Solana'), which implies when it is safe to call. It does not, however, state when to prefer this over buy_crypto_price or the buy_coin_* family, nor any exclusion such as freshness or rate limits.

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