Skip to main content
Glama

SouthPow crypto & market data

buy_tok_EQB

Paid. Equilibria Finance (EQB) 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/EQB.

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

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, the description carries the behavioral burden and does so well for an agent that must consider spend: it discloses a fixed $0.05 USDC charge, payment chains (Base or Solana), no account/API key requirement, and that failed calls are not charged. It omits rate limits, idempotency/caching behavior, and what constitutes a 'failed' call, which is the main remaining gap.

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?

Three tight sentences front-load payment status, then the data payload, then the commercial mechanics and endpoint. The telegraphic fragment style ('Paid.', '$0.05 USDC on Base or Solana.') is efficient but slightly clipped; nothing is wasted, though it reads more like a price tag than prose.

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, no-output-schema price lookup, the description covers what is returned, what it costs, where to pay, and what happens on failure — enough for an agent to call it correctly. It stops short of describing the response shape (field names/nesting) or freshness/latency, which an agent evaluating data quality might want.

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; the baseline of 4 applies. The description correctly implies no inputs are needed.

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 the concrete resource ('Equilibria Finance (EQB) price') and the exact payload fields returned: live USD price, 24h change, market-cap rank. It resolves the ticker to a full asset name, which the name 'buy_tok_EQB' alone does not. It does not explicitly distinguish itself from the hundreds of sibling buy_tok_* price tools beyond the ticker, but the resource is unambiguous.

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?

No explicit when-to-use or when-not-to-use guidance and no named alternative (e.g., buy_crypto_price or buy_coin_*). Usage is implied by the description of what data comes back, and the cost/payment terms do inform a use decision, but the agent gets no routing instructions.

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