Skip to main content
Glama

SouthPow crypto & market data

buy_stable_usdf-219

Paid. Astherus (USDF) stablecoin live: price vs peg, supply, 1d/7d/30d supply change, supply per chain (DefiLlama data). $0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/stablecoins/usdf-219.

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_usdf-219"
  }
}

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 burden and does a decent job: it discloses the paid model, exact price and payment chains, that authentication is not required, and that failed calls are free, all of which are behavioral facts not derivable from the empty input schema. It does not describe the response shape, data freshness, 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-loads the two things an agent most needs (paid, and what data), then payment mechanics, then the endpoint. Dense and low-waste; the leading 'Paid.' slightly duplicates the '$0.01 USDC' sentence, but nothing bloats the text.

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 lookup with no output schema and no annotations, the description covers what the payload contains, the cost, the payment rails, and the failure-billing policy, which is close to what an agent needs to decide and call. The main residual gap is that the concrete return format is only implied by the field list.

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. The fixed URL reinforces that all scoping is baked into the endpoint rather than passed as arguments.

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?

Names the specific asset (Astherus USDF) and the exact data returned: price vs peg, supply, 1d/7d/30d supply change, and per-chain supply, with the upstream source (DefiLlama). That is enough to tell it apart from generic siblings like buy_crypto_price or buy_tvl_*. It does not, however, explain how it differs from the near-identical sibling buy_stable_usdf.

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?

The description tells you the cost ($0.01 USDC on Base or Solana), that no account or API key is needed, and that failed calls are not charged, which is useful pre-call context. It gives no guidance on when to choose this over buy_stable_usdf or buy_cp_stablecoins-check, which matters given the closely overlapping 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