Skip to main content
Glama

SouthPow crypto & market data

buy_tok_LOBO

Paid. LOBO•THE•WOLF•PUP (LOBO) 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/LOBO.

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

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, the description carries the full burden and does reasonably well: it discloses that calls are paid ($0.01 USDC), the accepted chains (Base, Solana), that no auth is required, and that failed calls are not charged — an important billing behavior. It still omits latency/refresh cadence and whether the price is cached or real-time despite calling it 'live'.

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' and the returned fields, then pricing, then access terms — a sensible order with no filler. The telegraphic fragments and a bare URL at the end are slightly rough but each sentence carries information.

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 tool with no output schema, the description adequately covers what comes back (price, 24h change, rank) and the payment mechanics needed to invoke it successfully. The main residual gap is that no output schema means field names/types must be guessed from prose.

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 and there is nothing the description could add. The embedded URL confirms the token is hardcoded, which is consistent with the empty schema.

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 verb (buy/fetch price) and resource (LOBO token) and enumerates the returned fields: live USD price, 24h change, market-cap rank. It is distinguishable from the mass of buy_tok_* siblings by naming the exact token contract ticker, but it never contrasts itself with the generic buy_crypto_price or explains why LOBO has its own tool.

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 'Paid. ... $0.01 USDC on Base or Solana' framing makes the commercial prerequisite clear, and 'No account, no API key' removes setup ambiguity. However there is no explicit when-to-use/when-not guidance relative to buy_crypto_price or other price tools, leaving routing to be inferred from the token name alone.

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