Skip to main content
Glama

SouthPow crypto & market data

buy_tok_DRAMB

Paid. Roundhill Memory ETF (bStocks Tokenized ETF) (DRAMB) 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/DRAMB.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose cost ($0.05 USDC on Base or Solana), the absence of accounts/API keys, and that failed calls are not charged, which is genuinely useful. However, it omits the most consequential mechanics for a paid tool: how payment is actually presented (x402/wallet flow), whether calls are billed per attempt or per success, and any rate limits, so an agent cannot predict the payment interaction.

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?

Front-loaded with the 'Paid.' flag and asset identity, then pricing, then payment mechanics. It is dense but not padded. The trailing raw URL earns only marginal place, since it duplicates what the tool call already abstracts.

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 price lookup with no output schema, the description covers the return fields (price, 24h change, market-cap rank), the cost, the payment chains, and the free-on-failure policy. The remaining gap is the payment handshake, which matters because the tool is explicitly paid and has no annotations to fall back 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 tool takes zero parameters, which is the baseline-4 case; the description correctly implies nothing needs to be supplied. It adds slight value by naming exactly which asset is returned, so no parameter-like selection is left ambiguous.

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 states a specific resource and returns: 'Roundhill Memory ETF (bStocks Tokenized ETF) (DRAMB) price: live USD price, 24h change and market-cap rank.' The named asset differentiates it from the numerous buy_coin_*/buy_stable_* siblings, but it never explains the tok-vs-coin-vs-stable naming split, so the agent must infer that routing rule.

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 specific asset and the 'Paid' marker, but there is no explicit when-to-use statement and no named alternative (e.g. a broader buy_crypto_price or another DRAMB variant). The agent has to infer that this is the single-asset quote tool rather than a screener or list endpoint.

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