Skip to main content
Glama

SouthPow crypto & market data

buy_stable_buidl

Paid. BlackRock USD (BUIDL) stablecoin live: price vs peg, supply, 1d/7d/30d supply change, supply per chain (DefiLlama data). $0.002 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/stablecoins/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_stable_buidl"
  }
}

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 full burden and does substantial work: it discloses that the call is paid ($0.002 USDC), the accepted payment chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged. The upstream data source (DefiLlama) and endpoint URL are also given. It does not describe response shape or latency, which keeps 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?

It opens with the single most decision-relevant token ('Paid.'), then states the payload, then pricing and access terms, then the URL. Every clause carries information an agent needs to either select the tool or execute the call, 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 paid data endpoint with no annotations and no output schema, the description covers purpose, data source, cost, payment rails, and failure billing. The main residual gap is response format and identification of the sibling that covers yield rather than peg/supply data. That gap is minor given the tool's simplicity.

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 is an empty object with zero properties, so there is nothing for the description to disambiguate. The baseline for a parameterless tool applies, and the description correctly does not invent parameters.

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 specific resource (BlackRock USD / BUIDL stablecoin) and enumerates exactly the metrics returned: price vs peg, supply, 1d/7d/30d supply change, and per-chain supply. That is far more specific than the name alone. It stops short of naming the nearest siblings (buy_stable_usdc, buy_yields_token_buidl), so an agent must infer the distinction from the listed fields rather than being told.

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 context is implied by 'live' and the DefiLlama attribution, and the payment terms make the cost of calling it explicit. However, there is no statement of when to prefer this over buy_stable_usdc or buy_yields_token_buidl, and no note on data freshness or call frequency. An agent can tell what it gets but not clearly when it is the right choice among ~700 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