Skip to main content
Glama

SouthPow crypto & market data

buy_tok_MAX

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

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

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 supplied, the description carries the burden and does well: it discloses the $0.05 USDC cost, accepted chains (Base or Solana), that no account or API key is needed, and the important failure policy that failed calls are not charged. It stops short of describing rate limits, latency, or the shape of the returned payload.

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?

The definition is four short, front-loaded sentences that each carry a distinct fact: what it returns, what it costs and where, that no auth is required, and the failure-charge policy. The redundant 'MAX (MAX)' phrasing is the only wasted element.

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, output-schema-less tool, the description covers the salient unknowns: cost, payment chains, auth, and billing on failure, plus the backing URL. The main remaining gap is that the return fields (price, 24h change, rank) are named but not described in shape or units, which matters since no output schema exists.

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 and the baseline of 4 applies. The description correctly implies the token is fixed in the endpoint rather than passed as 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?

The description names a specific resource and payload: live USD price, 24h change and market-cap rank for the MAX token, which an agent can distinguish from unrelated siblings. It does not, however, explain how it differs from near-identical siblings such as buy_coin_MAX or buy_crypto_price, so the differentiation is token-specific only.

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: 'MAX (MAX) price' tells the agent what it fetches, but there is no explicit statement of when to choose this over buy_coin_MAX, buy_crypto_price, or buy_tok_* alternatives. The payment and no-account notes give context for committing to the call but do not route between siblings.

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