Skip to main content
Glama

SouthPow crypto & market data

buy_tok_DEXE

Paid. DeXe (DEXE) 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/DEXE.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/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 disclose genuinely useful behavior: the call is paid, costs $0.05 USDC on Base or Solana, requires no credentials, and failed calls are not charged. It says nothing about rate limits, latency, response shape, or caching, so an agent cannot reason about freshness or repeated-call cost.

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-loaded with 'Paid', then the payload, then cost, then access terms — a sensible priority order for an agent deciding whether to spend money. Every clause is short, though the trailing raw URL is arguably redundant with the tool name and endpoint naming convention.

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 parameterless paid price lookup with no output schema, the description covers cost, payment rails, auth, failure billing, and returned fields — enough to call it safely. The only material omission is disambiguation from buy_coin_DEXE and buy_crypto_price, which matters in a sibling set this large.

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, which is the baseline-4 case; the description correctly implies there is nothing to supply and names the single asset in the tool name itself.

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?

States a specific resource (DeXe / DEXE) and exactly what data comes back: live USD price, 24h change, and market-cap rank. It does not distinguish this from the coexisting siblings buy_coin_DEXE and buy_crypto_price, so an agent cannot tell from the description alone which of the three to call.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance and no named alternative. The 'No account, no API key' line describes access prerequisites rather than selection criteria, and in a namespace containing three plausible DEXE/price tools that omission is the main practical gap.

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