Skip to main content
Glama

SouthPow crypto & market data

buy_tok_EAT

Paid. WYDE: End Hunger (EAT) 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/EAT.

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

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, the description carries the full burden and does well: it discloses that the call is paid ($0.05 USDC on Base or Solana), that no account or API key is needed, and critically that failed calls are not charged — a real billing risk disclosure. It does not state rate limits, latency, or what an error/refund looks like, which keeps it from 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Dense but front-loaded: cost and payment rails come first, then what is returned, then the endpoint. The telegraphic fragments ('Paid. WYDE: End Hunger (EAT) price:') are slightly clipped, and the raw URL is somewhat redundant next to the tool itself, but nothing is wasted.

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-param, output-schema-less paid price lookup, the description covers the essentials an agent needs: the asset, the three returned fields, the price, the payment chains, and the failure-billing policy. Missing only finer return-format details (e.g., JSON shape, currency/units of the price), which are minor.

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 baseline of 4 applies. The description adds useful detail about what the returned values are (USD price, 24h change, market-cap rank), which complements the empty schema rather than duplicating it.

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 the specific asset ('WYDE: End Hunger (EAT)') and enumerates exactly what is returned: live USD price, 24h change, and market-cap rank. This cleanly separates it from the hundreds of sibling buy_tok_* tools by token. It stops short of a 5 because the verb is only implied and there is no explicit contrast with buy_crypto_price, the general-purpose alternative.

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 rather than stated: an agent can infer this is the tool to call when it needs EAT pricing specifically. There is no explicit when-to-use/when-not guidance and no pointer to buy_crypto_price or other siblings for different assets, so selection relies on matching the token name.

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