Skip to main content
Glama

SouthPow crypto & market data

buy_tok_BDCA

Paid. BitDCA (BDCA) 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/BDCA.

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

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 supplied, the description carries the full burden and does well: it discloses the paid model ($0.05 USDC), accepted payment chains (Base or Solana), the absence of auth requirements, and the failure-billing policy ('Failed calls not charged'), plus the underlying endpoint URL. What it omits is whether the price is a snapshot vs streaming, rate limits, or how the payment is actually transacted per call, keeping it 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.

Conciseness5/5

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

A tight, front-loaded block: cost first, then payload contents, then payment rails, then auth and billing guarantees, then the raw URL. Every clause adds decision-relevant information and 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 purchase endpoint with no annotations and no output schema, the description supplies the essentials: what data comes back, what it costs, how to pay, and what happens on failure. The lack of output schema means the enumeration of returned fields does real work. It could be more complete with response shape or freshness/latency details, but nothing critical for invocation is missing.

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 there is no parameter semantics to explain and the baseline is 4. The description correctly implies no arguments are required by not introducing any, and the token and endpoint are baked into the tool identity.

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 exact resource (BitDCA / BDCA live USD price) and enumerates the fields returned: price, 24h change, and market-cap rank. The 'Paid' prefix and USDC price make clear this is a paid access call, distinguishing it from the hundreds of sibling buy_tok_* entries only by ticker, which is adequate given the naming convention. It stops short of a crisp verb+resource phrasing like 'Purchase a price quote for BDCA', but an agent can identify what it gets.

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?

It implicitly tells the agent this is the tool for BDCA pricing and provides decision-relevant context (no account or API key needed, $0.05 charge, failed calls free), which helps an agent weigh whether to call it. However, there is no explicit when-to-use versus when-to-use-an-alternative guidance, e.g. no pointer to a free crypto price tool or a bundled quote for multiple tokens.

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