Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ETHIRD

Paid. Ember Third Eye (ETHIRD) 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/ETHIRD.

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

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 so well: it discloses that the call is paid ($0.05 USDC), which chains settle payment (Base or Solana), that no account or API key is required, and that failed calls are not charged. The main omissions are rate limits and whether payment is charged automatically per invocation.

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?

It leads with 'Paid.' so the cost implication is front-loaded, then packs the returned fields, price, payment chains, auth requirements, failure policy and endpoint URL into a few dense clauses. No sentence is filler.

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 tool with no output schema, the description adequately compensates by enumerating the three returned data points and spelling out the payment and failure model. What remains unstated is the response shape beyond those field names and the mechanics of how the $0.05 charge is collected.

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 semantics to explain and the baseline of 4 applies. The description correctly does not waste space describing inputs.

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 (Ember Third Eye / ETHIRD) and states exactly what it returns: live USD price, 24h change and market-cap rank. That is a clear verb-plus-resource statement. It does not explain how it relates to nearby siblings such as buy_crypto_price or buy_coin_* tools, so an agent must infer that this is the per-asset variant for ETHIRD.

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 only implied: an agent infers it should call this when it needs ETHIRD price data. The description gives purchasing context (cost, chains, no account/API key, no charge on failure) but never states when to prefer this over the generic buy_crypto_price tool or the buy_coin_* family, and offers no exclusions.

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