Skip to main content
Glama

SouthPow crypto & market data

buy_tok_MANTA

Paid. Manta Network (MANTA) 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/MANTA.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 ($0.05 USDC), the accepted payment rails (Base or Solana), that no account or API key is needed, and that failed calls are not charged. Missing only rate limits, latency/freshness, and return format.

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?

Roughly five short clauses, front-loaded with 'Paid.' so cost is the first thing the agent sees, followed by payload, price details, billing terms, and endpoint. No filler and no repetition of the schema or name beyond what is needed.

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 paid endpoint, the description covers what is returned (USD price, 24h change, market-cap rank), how to pay, and that failures are free. Only response encoding and data freshness are unstated, which are minor for a single-value price 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 tool takes zero parameters, so there is no parameter semantics to explain; baseline is 4. The description correctly fixes the token implicitly via the tool name and URL path, leaving nothing for the caller to supply.

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 specific resource and data payload: 'Manta Network (MANTA) price: live USD price, 24h change and market-cap rank.' The token symbol in the name plus the description cleanly separates it from lookalikes such as buy_tok_MANTRA and buy_coin_MANTA. It never explicitly contrasts itself with buy_crypto_price, so sibling differentiation is implicit rather than stated.

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?

Context of use is implied (you want MANTA price data), and the cost/no-account/no-key lines tell the agent it can be called without setup. There is no explicit when-to-use versus when-not guidance and no naming of alternatives like buy_crypto_price for multi-asset lookups. The reader must infer the routing decision.

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