Skip to main content
Glama

SouthPow crypto & market data

buy_tok_BABY

Paid. Babylon (BABY) 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/BABY.

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

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 well: it discloses that the call is paid, the exact price and accepted chains, that no account or API key is required, and the important failure semantic that failed calls are not charged. Missing only rate limits and response latency/shape, which keeps it off a 5.

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?

Very short and front-loaded: payload description first, then price/rails, then auth and failure terms, then the URL. The telegraphic fragments ('Paid.', 'No account, no API key.') are efficient though slightly staccato; nothing is redundant.

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 supplies what an agent actually needs: the exact fields returned, the cost and payment chains, the absence of auth, and failure charging behavior. It also gives the raw endpoint for verification. Only rate limits and latency are unaddressed.

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 input schema has zero parameters, so the baseline is 4 and the description correctly introduces no parameter semantics. It adds no noise about nonexistent arguments, which is the right behavior for a fixed-purpose endpoint.

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 and payload: 'Babylon (BABY) price: live USD price, 24h change and market-cap rank.' An agent can tell exactly which asset and which fields it gets, distinguishing it from the adjacent buy_coin_* and other buy_tok_* tools. It stops short of explicitly naming a sibling alternative, but the token scope is unambiguous.

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 implied rather than stated: fetch this when you want BABY's live price. There is no explicit 'use this instead of X' routing among the hundreds of sibling price tools, and no guidance on when a paid single-token call is preferable to a broader endpoint. The payment context ('$0.05 USDC on Base or Solana') implies deliberate, budget-aware invocation but never says so.

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