Skip to main content
Glama

SouthPow crypto & market data

buy_tok_EKUBO

Paid. Ekubo Protocol (EKUBO) 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/EKUBO.

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

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?

No annotations exist, so the description carries the full burden, and it does disclose real behavior beyond the name: a fixed $0.05 USDC cost payable on Base or Solana, no authentication required, no charge on failure, and the underlying endpoint. Not covered are payment mechanics (how the USDC is collected), rate limits, or the response shape/format.

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.' and the essential data returned, then cost, then prerequisites — an agent can decide in one read. The raw endpoint URL is the only sentence that may not earn its place for a zero-arg tool, though it does support debugging.

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?

There is no output schema, so the description sensibly enumerates the returned fields (price, 24h change, market-cap rank). Combined with the payment and failure-charging notes, an agent has enough to decide and invoke; only the response encoding and payment flow remain unspecified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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; the schema is empty and fully described. The description correctly implies the ticker is fixed by the tool identity rather than passed in, which prevents an agent from hunting for 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?

States a concrete resource (Ekubo Protocol / EKUBO) and exactly what comes back: live USD price, 24h change and market-cap rank. The per-token naming convention separates it from the other buy_tok_* siblings, but the description never names an alternative (e.g. a general crypto-price tool or the spot-market buy_coin_EKUBO) that an agent should weigh it against.

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?

Gives useful preconditions — paid, no account, no API key, failed calls not charged — which tells the agent it can call it autonomously without setup. It stops short of when-to-use guidance: nothing says when to prefer this over a generic price endpoint or over the sibling token tools, so selection among the ~700 buy_tok_/buy_coin_ entries is left to inference from the tool 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