Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ENJ

Paid. Enjin Coin (ENJ) 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/ENJ.

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

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 at all, the description carries the full burden and does it well: it declares the tool is paid, the exact price and accepted chains, that no credentials are needed, and that failed calls are not billed. It also enumerates what the response contains (price, 24h change, market-cap rank) and gives the endpoint URL. It stops short of explaining how the payment is actually transacted with zero parameters and whether data is real-time vs cached.

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.' then the data payload, then the price/access terms, then the URL — a sensible ordering with no filler. Slightly uneven in that payment logistics consume more space than the actual data description, but every sentence conveys usable information.

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, single-asset price lookup with no output schema, the description covers what it returns, what it costs, and how to reach it directly. The remaining gaps — data freshness, payment mechanics, and overlap with buy_coin_ENJ — are real but secondary 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 schema has zero properties, which is the baseline-4 case. The description correctly implies a parameterless call scoped to a single fixed asset, and the URL confirms the symbol is baked into the path rather than passed as an argument.

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 and verb: live USD price, 24h change and market-cap rank for Enjin Coin (ENJ). That is far more than a restated name. However, it never distinguishes itself from the near-identical sibling 'buy_coin_ENJ' or from 'buy_crypto_price', so among a very large family of look-alike tools the agent gets no help choosing.

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?

It gives cost and access context ('$0.01 USDC on Base or Solana', 'No account, no API key', 'Failed calls not charged'), which is real guidance about when it is viable to call. What it lacks is routing guidance: nothing says when to prefer this over buy_coin_ENJ, buy_crypto_price, or how it relates to the buy_cp_* category tools.

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