Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ECTE

Paid. EurocoinToken (ECTE) 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/ECTE.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden, and it does disclose useful commercial behavior: paid at $0.01 USDC on Base or Solana, no account or API key needed, and failed calls are not charged. It stops short of explaining how payment is actually transacted, whether price data is cached or how fresh 'live' is, or what an error or insufficient-funds response looks like.

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?

Tightly front-loaded: the payment flag comes first, then the resource and its fields, then cost, then access terms, then the source URL. Six short clauses with no filler, though the bare URL at the end is of marginal value to an agent.

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-argument price lookup with no output schema, the description is close to sufficient: it names the three returned fields, the cost and payment chains, and the absence of auth. The main residual gap is that the payment mechanics of a 'Paid' tool are left unexplained.

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 applies. The description is correct to spend its words on scope and pricing rather than on nonexistent arguments.

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?

Names a specific asset (EurocoinToken/ECTE) and enumerates exactly what the call returns: live USD price, 24h change, market-cap rank. This distinguishes it from non-token siblings like buy_fx_eur or buy_tvl_base, though it never explains its relationship to buy_crypto_price or the parallel buy_coin_* family, so the differentiation is by ticker rather than by stated scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance. The agent must infer that this is the ECTE price endpoint purely from the ticker in the name, and nothing tells it whether buy_crypto_price or a buy_coin_* sibling would also return ECTE data or when to prefer one over the other.

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