Skip to main content
Glama

SouthPow crypto & market data

buy_tok_EDX

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 so unusually well for a paid endpoint: it discloses the price ($0.05 USDC), accepted payment chains (Base or Solana), that no account or API key is required, and that failed calls are not charged. It omits rate limits and any note on response freshness, so it stops short of full disclosure.

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." so the agent knows the cost implication before anything else, then the data content, then payment/access logistics. The trailing raw URL is of marginal value to an MCP caller and keeps it from being perfectly tight, but every other clause earns its place.

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 price tool with no output schema, the description names the three returned values and fully covers the unusual risk factor (this call costs money, but failures are free). Lacking rate-limit or freshness detail is a minor gap for a tool this simple.

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, so the schema baseline is 4 and there is no parameter meaning for the description to add. It correctly spends its words on payment and return fields instead of restating an 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?

States a specific verb+resource: a live USD price feed for edeXa (EDX), naming the returned fields (USD price, 24h change, market-cap rank). The ticker in the tool name plus "edeXa (EDX)" in the description lets an agent tell it apart from the hundreds of sibling buy_tok_* tools, though it never explicitly says "this tool is for EDX only."

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?

The word "Paid" plus the cost line establishes that this is a paid purchase rather than a free lookup, which is real usage context. However, it never states when to prefer this over adjacent price tools (buy_crypto_price, buy_coin_* variants) or what happens if the agent needs multiple tokens, leaving selection to be inferred from the ticker alone.

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