Skip to main content
Glama

SouthPow crypto & market data

buy_tok_SN24

Paid. OMEGA Labs (SN24) 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/SN24.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/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 cost ($0.01 USDC), accepted payment rails (Base or Solana), that no account or API key is needed, and that failed calls are not charged. That is exactly the operational context an agent needs before spending money. It stops short of describing response format, latency, or what counts as a 'failed' call.

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?

Six short telegraphic clauses, front-loaded with 'Paid.' and the returned fields, then cost, rails, auth, failure policy, and URL. No filler, though the clipped fragment style (bare '$0.01 USDC on Base or Solana') trades polish for density.

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 paid lookup with no output schema, the description covers the essentials: what data returns, what it costs, how to pay, and that failures are free. Only minor gaps remain, such as response shape or data freshness, which matter little for a single price tick.

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 input parameters, so there is nothing for the description to disambiguate; the baseline for a zero-param tool applies. The description correctly conveys that the call is parameterless by fixing the asset and endpoint in the text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete resource (OMEGA Labs / SN24) and enumerates exactly what comes back: live USD price, 24h change, market-cap rank. The verb is implicit in the 'buy_' prefix and the paid-call framing, so an agent can tell this apart from the other buy_tok_SN* variants without opening anything.

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: pay $0.01 and get SN24 price data. It never states when to prefer this over buy_crypto_price or the other subnet token tools, nor any condition under which the call should be skipped. Acceptable for a zero-parameter single-asset lookup, but explicit routing guidance is absent.

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