Skip to main content
Glama

SouthPow crypto & market data

buy_tok_B

Paid. BUILDon (B) 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/B.

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

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 the call is paid ($0.05 USDC on Base or Solana), that no account or API key is needed, that failed calls are not charged, and gives the endpoint URL. It does not explain the payment flow mechanics, rate limits, or the shape of the response, which leaves some behavioral gaps.

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 front-loaded with the paid flag and the resource, then layers cost, auth, and billing policy in tight fragments. The style is telegraphic rather than prose, but every clause carries information and 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, single-asset price lookup with no output schema, the description covers the essentials an agent needs before calling: what comes back, what it costs, which chains, and that failures are free. Only the response format and the payment protocol are left implicit.

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. The description correctly implies no inputs are required by stating 'no account, no API key', which reinforces the no-argument invocation model.

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 the specific resource (BUILDon / B token) and the exact payload: live USD price, 24h change, and market-cap rank. That is enough to distinguish it from the hundreds of sibling buy_tok_* tools, but it never states how it differs from the generic buy_crypto_price or buy_coin_* variants covering the same asset class.

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 can infer this is the tool to call when it wants the B token's price. There is no explicit when-to-use or when-not-to-use guidance, and no mention of the obvious alternatives (buy_crypto_price, buy_coin_* families) that a selecting agent will be comparing against.

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