Skip to main content
Glama

SouthPow crypto & market data

buy_tok_EWT

Paid. Energy Web Token (EWT) 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/EWT.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/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 the paid cost ($0.05 USDC), accepted payment chains (Base or Solana), absence of account/API key, the failure-refund policy ('Failed calls not charged'), and the endpoint URL. That is materially useful behavioral context beyond what a bare schema provides; only latency/rate-limit behavior is unspecified.

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?

Six short clauses, front-loaded with what it is, then what it returns, then pricing/failure terms, then the URL. No filler; every sentence carries information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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, paid endpoint, the description covers what it returns, how much it costs, how to pay, that no auth is needed, the failure-billing policy, and the URL. Nothing an agent needs 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 tool takes zero parameters, so there is no parameter meaning to add — the baseline of 4 applies. The description correctly implies a parameterless call by giving a fixed endpoint URL per token.

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 a specific resource (Energy Web Token / EWT price) and enumerates exactly what is returned: live USD price, 24h change, and market-cap rank. It is immediately clear which token this tool covers. It stops short of 5 because with hundreds of buy_tok_* siblings plus a generic buy_crypto_price tool, it never explicitly distinguishes itself from the generic 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 'call this when you need EWT price data.' The description usefully covers cost, payment chains, and no-auth requirements, but gives no when-not guidance and never mentions the generic buy_crypto_price sibling that could also serve price lookups.

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