Skip to main content
Glama

SouthPow crypto & market data

buy_tok_DETO

Paid. Delta Exchange (DETO) 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/DETO.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/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 it does well: it discloses the paid model ($0.05 USDC), the accepted payment rails (Base or Solana), the absence of account or API-key requirements, and that failed calls are not charged. It stops short of rate limits, latency, or data freshness, 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.

Conciseness5/5

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

Five short fragments, front-loaded with the paid flag and the data returned, then cost, then access requirements. Nothing is redundant, and the raw endpoint URL is useful for an x402-style paid call.

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-annotation, no-output-schema tool, the description covers what is returned, what it costs, how to pay, and the error-charging policy. It could go further by sketching the response shape or stating how fresh the price is, but an agent has enough to call it correctly.

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; the baseline applies. The symbol is baked into the tool name and confirmed in prose, which is the only parameter-like information an agent needs here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific resource and payload: "Delta Exchange (DETO) price: live USD price, 24h change and market-cap rank." It also expands the ticker, which matters because hundreds of sibling buy_tok_* tools differ only by symbol and an agent must know DETO means Delta Exchange to pick the right one.

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: buy this endpoint when you want the DETO price. There is no explicit statement about when to prefer it over the generic buy_crypto_price tool or over any other buy_tok_* sibling, and no guidance on repeat calls or caching.

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