Skip to main content
Glama

SouthPow crypto & market data

buy_stable_dola

Paid. Dola (DOLA) 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/dola.

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

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 at all, the description carries the full behavioral burden and does well: it discloses that the call is paid, the exact price ($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. What is missing is any statement about response shape beyond the field list, latency, or rate limits, which keeps it from 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.

Conciseness4/5

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

Front-loaded with 'Paid.' then the data scope, then cost/payment mechanics, then the endpoint URL — a sensible ordering for an agent deciding whether to spend money. It is telegraphic rather than verbose, though the raw URL is marginally noisy for a tool an agent invokes through MCP rather than by hand.

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 data endpoint, the description supplies the two things an agent actually needs: what data is returned and what it costs to get it. Return fields are enumerated in prose, which compensates for the absent output schema. Only the lack of sibling differentiation keeps it below a 5.

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 nothing for the description to disambiguate; baseline 4 applies. No misleading parameter claims are made.

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 resource (DOLA stablecoin) and enumerates exactly what data comes back: price vs peg, supply, 1d/7d/30d supply change, and per-chain supply from DefiLlama. That is far more concrete than a tautology. It loses a point because it never distinguishes itself from near-identical siblings like buy_coin_DOLO or the other buy_stable_* endpoints, so an agent must infer that this one is the DOLA-specific stablecoin-metrics feed.

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 only implied: the agent can infer this is for DOLA stablecoin analytics, and the pricing lines clarify the commercial terms of calling it. There is no explicit when-to-use or when-not-to-use guidance, and no pointer to buy_coin_DOLO (price) or other buy_stable_* tools as alternatives, which is the main ambiguity in a catalog this dense.

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