Skip to main content
Glama

SouthPow crypto & market data

buy_tok_DIVI

Paid. Divi (DIVI) price: live USD price, 24h change and market-cap rank. $0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/DIVI.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

With no annotations present, the description carries the full behavioral burden and does so well: it discloses the paid model ($0.01 USDC on Base or Solana), that no account or API key is required, and that failed calls are not charged. What it omits is the response encoding and whether repeated calls are cached, which is a minor residual gap rather than an omission of consequence.

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?

Six short clauses, each doing distinct work: payment status, payload, price and rails, auth requirements, billing policy, endpoint URL. The cost flag is front-loaded as the first word, which is exactly the information an agent needs before invoking a paid tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a parameterless, single-value paid lookup with no output schema and no annotations, the description covers the three things that matter: what data comes back, what it costs and on which chains, and the billing behavior on failure. Nothing an agent needs in order to decide and call is missing.

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 has zero properties, so there are no parameters to disambiguate and the baseline is 4. The description correctly signals that no identifier needs to be supplied, consistent with a single-asset endpoint.

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 exact resource (Divi / DIVI) and enumerates the returned data points: live USD price, 24h change, and market-cap rank. It is distinguishable from generic siblings like buy_crypto_price only via the ticker embedded in the name, but the payload is stated precisely enough that an agent knows what it is buying.

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 only implied: an agent infers it should call this when it needs DIVI pricing. There is no explicit guidance on when to prefer this over buy_coin_DIVI (a token-listing sibling that likely also covers DIVI) or the general buy_crypto_price endpoint, and no stated exclusions or freshness/staleness caveats.

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