Skip to main content
Glama

SouthPow crypto & market data

buy_tok_DESSA

Paid. Dessa (DESSA) 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/DESSA.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden and does real work: it flags the tool as paid, states the exact cost ($0.01 USDC), names the accepted payment rails (Base or Solana), confirms no account or API key is needed, and states that failed calls are not charged. That covers cost, auth and failure billing, which is the information an agent most needs before spending. It does not describe the error response or the exact payload shape beyond the three data fields.

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 paid flag leads, the payload is described next, then cost/payment/auth/failure terms, then the endpoint URL. It is telegraphic but every fragment carries decision-relevant information, with no filler or redundancy.

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-output-schema paid lookup, the description supplies the commercial model, payment rails, auth posture and failure billing, which is what an agent needs before invoking. The remaining gap is what a response or error actually looks like, though the three returned fields are at least enumerated.

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 declares zero properties, so there is nothing for the description to disambiguate; the baseline of 4 applies. The description implicitly confirms the token is fixed by the tool itself rather than passed as an argument, which is consistent with the empty schema.

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 resource and verb-equivalent: DESSA (Dessa) USD price with 24h change and market-cap rank. That distinguishes it from the hundreds of sibling buy_tok_* endpoints, which each target a different token. It stops short of clarifying how it relates to buy_coin_DESSA or buy_crypto_price, which appear in the sibling list and could plausibly cover the same data.

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 when-to-use or when-not-to-use guidance. The description never says to prefer this over buy_coin_DESSA, buy_crypto_price, or buy_polymarket-style alternatives, so an agent choosing among near-duplicate DESSA/price tools gets no routing signal.

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