Skip to main content
Glama

SouthPow crypto & market data

buy_tok_BP

Paid. Backpack (BP) 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/BP.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations at all, the description must carry the full behavioral burden, and it does disclose the important commercial traits: pay-per-call cost, accepted chains (Base, Solana), no auth, and the fact that failed calls are not charged. It stops short of stating response format, data freshness/caching, or rate limits, which matter for a live-price endpoint.

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 ('Paid.') and compressed into essentially one line covering purpose, price, payment rails, and endpoint. The trailing raw URL is slightly out of place versus the prose, but every clause carries information an agent needs before spending money.

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 return contents (price, 24h change, rank) and the cost/auth profile. Remaining gaps — response encoding and freshness — are modest for a tool of this complexity.

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 parameters, so the schema baseline applies; the description correctly implies the token is fixed in the endpoint URL rather than passed as an argument, which prevents an agent from searching for a missing symbol parameter.

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 the resource (Backpack / BP) and exactly what data comes back: live USD price, 24h change, and market-cap rank. That is specific enough to tell it apart from buys of other tokens, though it never contrasts with the generic buy_crypto_price sibling, so the differentiation is by token name only.

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 purchase context is implied rather than stated: 'Paid', '$0.01 USDC', 'no account, no API key' tell an agent the preconditions for calling, but nothing says when to prefer this over buy_crypto_price or a buy_coin_* tool, and there are no exclusions or fallback 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