Skip to main content
Glama

SouthPow crypto & market data

buy_tok_BUIDL

Paid. BlackRock USD Institutional Digital Liquidity Fund (BUIDL) 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/BUIDL.

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

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 provided, the description carries the full burden and does a solid job: it discloses the paid model, the exact price and accepted chains, the absence of account or API key requirements, the failure-charge policy, and the underlying endpoint URL. It stops short of describing response format, latency, or freshness guarantees, but the payment and access details are the operationally critical facts for a zero-parameter call.

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 description is front-loaded: the paid status leads, followed by the fund identity and returned fields, then pricing and access terms. Sentence fragments make it dense, and every sentence carries distinct information; the raw URL at the end is slightly noisy but still useful.

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 annotations and no output schema, the description supplies the returned fields, payment details, access requirements, and failure policy, which is close to what an agent needs. The only real gap is routing guidance among the many sibling token and yield tools for the same underlying asset.

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 no parameters, so there is no schema semantics for the description to compensate for; the baseline is 4. The description correctly implies the asset is fixed (BUIDL) rather than configurable, which matches the empty input schema.

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 verb-and-resource pair: it returns the live USD price, 24h change, and market-cap rank for BlackRock's BUIDL fund. That is far more than the tautological name restates, so an agent knows exactly what data comes back. It does not distinguish this from sibling tools serving the same asset, such as buy_stable_buidl or buy_yields_token_buidl, leaving the agent to guess which variant to 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?

Cost and access conditions are spelled out ($0.05 USDC on Base or Solana, no account or API key, failed calls not charged), which implies this is a paid endpoint to call when BUIDL pricing is needed. However, there is no explicit when-to-use guidance and no mention of when to prefer buy_stable_buidl, buy_yields_token_buidl, or buy_yields_protocol_blackrock-buidl instead, despite many near-identical siblings.

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