Skip to main content
Glama

SouthPow crypto & market data

buy_tok_DIT

Paid. DIAMOND TOKEN 💎 (DIT) 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/DIT.

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

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, the description carries the full burden and does relatively well: it discloses that the call is paid, the exact price and settlement chains, that no auth is required, and that failed calls are not billed. It omits rate limits, latency, and the response shape in any detail, which keeps it short of 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?

Cost and payment terms are front-loaded ('Paid.') and every sentence carries information an agent needs before spending money. The emoji in the token name and the raw URL are slightly extraneous for an agent, but nothing is redundant.

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 price lookup with no output schema, the definition covers what is returned, what it costs, how to pay, and failure billing — enough to decide and call safely. Missing only explicit return-format and freshness/latency details.

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 description correctly implies a parameterless call by hardcoding the endpoint and the token.

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 (DIAMOND TOKEN / DIT) and the exact payload (live USD price, 24h change, market-cap rank), so an agent knows what it gets back without opening a schema. It does not explicitly contrast with the many sibling buy_tok_* token tools or the near-named buy_tok_FDIT, so differentiation relies on the tool name alone.

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 by the resource named — 'get DIT price data' — with no stated conditions for choosing this over another token or price tool. It does supply operational preconditions (no account, no API key, $0.05 USDC on Base or Solana, failed calls not charged), which is useful context but not when-to-use guidance.

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