Skip to main content
Glama

SouthPow crypto & market data

buy_tok_GMX

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

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

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 supplied, the description carries the disclosure burden and does so well: it states the price ($0.05 USDC), the accepted chains (Base or Solana), that no account or API key is needed, that failed calls are not charged, and gives the concrete endpoint URL. What is missing is rate limiting, latency/freshness of the quote, and whether duplicate calls are billed.

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?

Three short sentences that are front-loaded ('Paid.') and each carry distinct information: what data, what it costs and where to pay, and the endpoint. No filler or restatement of the tool name.

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 tool this is close to complete: the agent knows the payload, the price, the payment chains, the failure-charge policy, and the URL. The only gaps are freshness of the price and the shape of the response, which the absent output schema leaves undocumented.

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 baseline is 4 and there is nothing about arguments the description could usefully add. It correctly avoids inventing parameters and instead spends its words on payload and payment terms.

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 specific resource and payload: 'GMX (GMX) price: live USD price, 24h change and market-cap rank', which is far more than the bare tool name conveys. It does not, however, distinguish this from the highly similar sibling buy_coin_GMX, so an agent cannot tell from the text alone which of the two to pick.

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 context is implied rather than stated: an agent can infer this is the way to get a live GMX quote, and the description notes it is paid and requires no account. There is no explicit when-to-use / when-not-to-use guidance and no mention of the near-identical buy_coin_GMX alternative, which matters given the enormous sibling list.

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