Skip to main content
Glama

SouthPow crypto & market data

buy_tok_EDENA

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it covers the economically important behaviors well: that the call costs money, the exact price and payment chains, absence of auth prerequisites, and that failures are not billed. It stops short of describing latency, rate limits or the response payload shape, which is the remaining gap for a paid endpoint with zero annotation coverage.

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 the paid flag and the tool's purpose, then cost, payment rails, prerequisites and the endpoint URL in short fragments; nothing is padded. Minor waste in the redundant 'EDENA (EDENA)' and the raw URL, which is informational rather than actionable for the agent.

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 purchase tool, the description covers what an agent needs before calling: what data comes back, what it costs, how to pay, and that failures are free. It could say more about the returned payload structure and delivery timing, but nothing essential to deciding whether to invoke it is missing.

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 properties, so there is nothing parameter-level to document; baseline is 4. The description usefully notes that the token is fixed by the tool rather than passed as an argument, which is the relevant semantic fact 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?

States a specific resource (EDENA token price) and enumerates exactly what the buyer receives: live USD price, 24h change and market-cap rank. The name plus description make clear this is the EDENA-specific variant among the many sibling buy_tok_* tools, so an agent can pick it without opening a schema.

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

Usage Guidelines4/5

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

Gives clear purchase context: it is a paid call at $0.01 USDC, payable on Base or Solana, with no account or API key required, and failed calls are not charged. It does not explicitly compare against a generic price alternative (e.g. buy_crypto_price) or state when to prefer this token-specific purchase over a broader one, but the conditions under which it is callable are unambiguous.

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