Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ELEPHANT

Paid. Elephant Money (ELEPHANT) 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/ELEPHANT.

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

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 full burden and does well: it discloses the cost ($0.01 USDC), the payment rails (Base or Solana), the absence of auth requirements, and the charging policy on failure. It does not cover data freshness or rate limits, which keeps it from a 5.

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?

It is front-loaded with 'Paid.' and then packs the resource, the return fields, the price, the payment chains and the endpoint into a few dense sentences. Every sentence carries information, though the raw URL at the end is of marginal use 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 no-parameter, no-output-schema fetch tool, the description covers what is returned, what it costs, how to pay and what happens on failure. Only cache/freshness and the shape of the payload are left unstated, which the absent output schema would otherwise absorb.

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 the schema baseline is 4. The description correctly implies there is nothing to supply and instead spends its words on the returned data and payment details.

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 (Elephant Money / ELEPHANT) and specifies the returned fields: live USD price, 24h change and market-cap rank. That is enough for an agent to distinguish it from the hundreds of parallel per-token siblings, though the 'buy_' prefix and paid-fetch semantics are only implied.

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 by the token-specific content; there is no explicit statement of when to pick this over the generic buy_crypto_price or other price siblings. The payment and 'failed calls not charged' notes do give an agent enough to judge whether to invoke it, but no exclusions are stated.

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