Skip to main content
Glama

SouthPow crypto & market data

buy_tok_EFI

Paid. ElevateFi (EFI) 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/EFI.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that the call is paid, the exact price ($0.05 USDC), the accepted payment chains (Base or Solana), that no account or API key is required, and that failed calls are not charged. Rate limits, latency, and caching behavior are not stated, 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the single most decision-relevant word ('Paid.'), then the payload, then the cost, then the endpoint. Roughly four short sentences with no filler; every clause (price, payment chain, no-key, no-charge-on-failure) carries decision value.

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 must explain both outputs and economics, and it does (price, 24h change, market-cap rank, plus full pricing terms). It stops short of describing error conditions other than non-charging, data freshness, or response shape, which are minor for a single-value lookup.

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 parameters, so there is nothing for the description to clarify; the baseline for a parameterless tool applies. The description correctly implies no inputs are needed and instead spends its words on cost and payment rails.

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 exact resource (ElevateFi / EFI) and enumerates the three returned fields: live USD price, 24h change, and market-cap rank. That is enough to distinguish it from the hundreds of sibling buy_tok_* tools, which differ only by token symbol. It lacks an explicit verb (e.g., 'fetch' or 'get'), but the intent 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 Guidelines4/5

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

Use context is clear: this is the paid per-token price endpoint for EFI, with no account or API key needed. However, it never names an alternative — notably the generic sibling buy_crypto_price or the buy_tok_* family pattern — so an agent must infer on its own that this tool should be picked only when EFI specifically is wanted.

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