Skip to main content
Glama

SouthPow crypto & market data

buy_tok_BORG

Paid. SwissBorg (BORG) 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/BORG.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the burden well: it discloses the paid model ($0.05 USDC on Base or Solana), that no account or API key is needed, that failed calls are not charged, and even the endpoint URL. What it does not cover is the response shape (JSON vs. text) or latency/rate-limit behavior, so it falls just short of full disclosure for a paid endpoint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The critical fact — 'Paid.' — is front-loaded in a single word, followed by what you get, what it costs, and what you don't need. Every clause carries information an agent needs before spending money; there is no filler.

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 purpose, fields returned, cost, payment rails, and non-charging-on-failure semantics — enough to decide and invoke safely. It only lacks a hint about the response format or typical latency, which is minor given there is no output schema to lean on.

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 there is nothing for the description to disambiguate; baseline 4 applies. The description correctly adds that no credentials or arguments are needed, confirming the tool is parameter-free by design.

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 verb-plus-resource: it fetches the live USD price, 24h change and market-cap rank for SwissBorg (BORG). The token symbol in the name and the description makes it distinguishable from the hundreds of sibling buy_tok_* and buy_coin_* endpoints. It stops short of explicitly saying how it relates to those families (e.g., why to pick this over a generic buy_crypto_price call).

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 description implies usage (you need BORG's current price) and notes there is no account or API key required, plus that failed calls are not charged. However it gives no explicit when-to-use / when-not-to-use guidance or named alternative, which matters given the enormous sibling set of per-asset price tools. Usage is inferable but not directed.

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