Skip to main content
Glama

SouthPow crypto & market data

buy_tok_DAI

Paid. Dai (DAI) 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/DAI.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the behavioral burden. It does useful work by disclosing cost ($0.05 USDC), payment rails (Base or Solana), no account or API key requirement, and that failed calls are not charged. However, it leaves out rate limits, latency, data freshness, and what a failure response looks like, so the tool's behavior is clear only in part.

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?

The text is a compact, front-loaded status note: it leads with 'Paid,' then lists return fields, price and payment details, billing policy, and the endpoint URL. Every clause conveys an actionable fact, with no filler or repetition.

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 zero-parameter, no-output-schema tool, the description covers the return fields, price, payment rails, auth posture, billing behavior, and endpoint. There is little else an agent needs before calling it, so this is close to complete for the tool's complexity.

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 parameters and 100% description coverage, so there is nothing for the description to clarify. Per the rubric, a zero-parameter tool starts at baseline 4. The description correctly adds no parameter detail and does not waste space inventing any.

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 combination: live USD price, 24h change, and market-cap rank for DAI. That is unambiguous about what the call returns. It earns only 4 because sibling tools such as buy_coin_DAI and buy_stable_dai look indistinguishable by name, and the description never explains how this tool differs from them.

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?

Use is only implied through the purpose statement and the cost terms: 'Paid... $0.05 USDC on Base or Solana.' There is no explicit when-to-use guidance and no mention of buy_coin_DAI or buy_stable_dai as alternatives or fallbacks. An agent must infer the correct tool from the name alone.

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