Skip to main content
Glama

SouthPow crypto & market data

buy_tok_EDEL

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 burden and does substantial work: it discloses the cost, the accepted payment chains, the absence of auth requirements, and the failure policy ('Failed calls not charged') — the last being exactly the kind of consequence an agent needs before spending. It does not explain the payment/challenge flow itself (how the $0.01 is actually remitted), which keeps it short of 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?

Front-loaded with 'Paid.' so the cost gate is the first thing seen, then the payload, then price/rails/terms, then the endpoint URL. Every clause adds information an agent would otherwise lack — nothing is restated from structured fields.

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 paid, parameterless data fetch with no output schema, the description covers what is returned, what it costs, how to pay, and what happens on failure — enough to call it correctly. The response shape and freshness/latency of the 'live' price are left unstated, which is a minor gap rather than a blocker.

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 and the schema is empty, so there is no parameter meaning to add; the description correctly avoids inventing any. Baseline for a 0-param tool applies.

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 and payload: 'Edel (EDEL) price: live USD price, 24h change and market-cap rank', which tells an agent exactly what data comes back. It does not position itself against the neighboring families (buy_coin_*, buy_crypto_price, buy_tok_* for other tickers), so the agent must infer the routing from the tool name alone.

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 implied by the name and payload description, and the payment mechanics ('$0.01 USDC on Base or Solana', 'No account, no API key') set expectations before calling. There is no explicit statement of when to prefer this over a general price aggregator sibling or what conditions would rule it out, so guidance is contextual rather than directive.

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