Skip to main content
Glama

SouthPow crypto & market data

buy_tok_EDEN

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

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

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 at all, the description carries the full behavioral burden and does well: it discloses that the call is paid ($0.05 USDC), supported payment chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged. It stops short of stating rate limits, latency, or price freshness, which matter for a paid quote endpoint.

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?

Front-loading 'Paid.' tells the agent the cost model before anything else, then purpose, price, payment rails, and endpoint URL follow in tight telegraphic order. No sentence 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 no-parameter, no-output-schema, no-annotation paid endpoint, the description supplies the cost, settlement chains, auth model, failure-charging policy, and returned fields. It could say more about response shape and price staleness, but nothing essential to invoke it correctly 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 parameters, so the baseline is 4. The 'no account, no API key' line usefully confirms the tool is callable with an empty argument object, which is the only parameter-level question an agent could have 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?

It names a specific resource (OpenEden / EDEN) and specifies exactly what is returned: live USD price, 24h change, market-cap rank. Because the sibling set contains one tool per token, the embedded ticker and project name are what let an agent pick the right one 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 Guidelines3/5

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

Usage is only implied by the ticker-specific naming; there is no explicit statement of when to choose this over the generic price tools (buy_crypto_price) or any related EDEN market view. Payment and access details are given, but selection conditions are left to inference.

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