Skip to main content
Glama

SouthPow crypto & market data

buy_tok_SWARM

Paid. SWARM ENGINE (SWARM) 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/SWARM.

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

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 supplied, the description carries the full burden and does well: it discloses that the call is paid ($0.01 USDC), the accepted chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged — the error/billing behavior is the kind of detail annotations would otherwise provide. It stops short of rate limits, latency, or whether the price is a snapshot versus streaming.

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.' followed by the payload description, then cost, payment rails, auth, billing behavior, and the endpoint URL — each clause adds a distinct fact. Slightly dense as a single run-on block, but no filler sentences.

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, no-output-schema tool, the description covers what comes back (price, 24h change, market-cap rank), what it costs, how to pay, and auth requirements. The main gap is response shape/formatting, which the missing output schema leaves undocumented.

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 there is nothing for the description to disambiguate; the baseline of 4 applies. The description correctly reflects the no-argument design by hardcoding the token in the URL rather than implying optional inputs.

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?

States a specific resource (SWARM ENGINE / SWARM token price) and the exact fields returned: live USD price, 24h change, market-cap rank. The ticker in the description ties it unambiguously to this variant among the many buy_tok_* siblings, so an agent can select it without opening the schema.

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: an agent infers 'call this when you want the SWARM price.' There is no explicit statement of when to prefer it over alternatives such as buy_crypto_price, buy_tok_USDC, or a general price endpoint, and no exclusions. The payment and auth notes are useful context but are not routing guidance.

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