Skip to main content
Glama

SouthPow crypto & market data

buy_tok_BERT

Paid. Bertram The Pomeranian (BERT) 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/BERT.

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

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 at all, the description carries the full behavioral burden and mostly meets it: it discloses the paid nature ($0.05 USDC), accepted payment chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged. Details left unstated include payment flow mechanics and whether the price is real-time or cached, which keeps this below 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?

The text is front-loaded with the resource and payload, then payment terms, then the endpoint. Every clause conveys actionable information. It reads as terse telegraphic fragments rather than sentences, but nothing is wasted.

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 endpoint with no output schema, the description supplies the essentials: what data comes back, the cost, the payment rails, and the no-auth guarantee. The absence of an explicit response shape and any note on rate limits or freshness prevents a top score.

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 per the baseline there is nothing for the description to disambiguate. It correctly adds no redundant parameter discussion and instead spends its words on payment and return content.

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 and enumerates exactly what is returned: live USD price, 24h change, and market-cap rank for Bertram The Pomeranian (BERT). An agent can identify the tool's job immediately. It does not, however, distinguish itself from near-identical siblings such as buy_crypto_price or the buy_coin_* family, so the boundary is left to inference.

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 by the payload description: call this when you need BERT's current price and market stats. There is no explicit statement of when to prefer this over buy_crypto_price or buy_coin_* alternatives, nor any exclusion criteria. An agent that already knows it wants BERT data can use it, but comparative routing is unsupported.

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