Skip to main content
Glama

SouthPow crypto & market data

buy_tok_BIB01

Paid. Backed IB01 $ Treasury Bond 0-1yr (BIB01) 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/BIB01.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/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 disclose real behavioral facts: it is a paid call costing $0.05 USDC on Base or Solana, requires no account or API key, and failed calls are not charged. Those are genuinely useful. It stops short of explaining how payment is authorized/broadcast, whether calls are idempotent, or what a failed-call response looks like, so a purchaser still has unknowns.

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?

It is short and front-loads the most decision-relevant fact ('Paid'), then the data payload, then price/rails, then the endpoint URL. The telegraphic phrasing is efficient, though the URL-as-last-token structure and sentence fragments are slightly choppy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter purchase endpoint with no output schema, the description covers cost, rails, auth-free access, and billing on failure, which is decent. It still leaves the output shape vague (field names/types for price, 24h change, rank) and says nothing about payment mechanics, which matters for a paid tool.

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 there is no parameter semantics to explain and the baseline is 4. The description correctly adds no misleading parameter hints.

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?

The description names a specific asset (Backed IB01 $ Treasury Bond 0-1yr) and enumerates the returned data: live USD price, 24h change, and market-cap rank. That is enough to distinguish it from the other asset-specific buy_tok_* siblings. It does not, however, explain how it differs from generic price siblings like buy_crypto_price or the corresponding buy_coin_* entry.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance and no named alternative. The reader must infer that this is the per-asset paid purchase endpoint for BIB01 pricing, and there is nothing telling them when to prefer buy_crypto_price, buy_coin_*, or buy_tok_* siblings instead.

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