Skip to main content
Glama

SouthPow crypto & market data

buy_tok_MX

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

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

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 behavioral load and does a decent job: it discloses the $0.05 USDC cost, the accepted payment chains (Base or Solana), that no account or API key is needed, that failed calls are not charged, and the underlying endpoint URL. It omits rate limits and response format, so it stops short of full disclosure.

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?

It is a single dense paragraph front-loaded with 'Paid.' followed immediately by what the caller gets. Every clause carries distinct information (data fields, price, rails, auth, billing policy, URL) with no repetition, though the 'MX (MX)' duplication is a minor blemish.

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?

There is no output schema, so the description must convey return content and it does by enumerating price, 24h change and market-cap rank. It also covers payment mechanics, which is the main risk for an agent calling a paid endpoint; only response format/serialization and freshness of the 'live' price are left unstated.

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; the baseline for parameterless tools applies. Nothing in the description misleads about inputs, and the endpoint URL confirms the token is fixed at call time.

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 resource (MX token) and enumerates the exact data returned: live USD price, 24h change and market-cap rank. That is specific enough to separate it from the many sibling buy_tok_* tools, although the 'MX (MX)' phrasing is redundant and the description never uses an explicit verb like 'fetch' or 'returns'.

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 by the data listed and by 'Paid... No account, no API key', but the description never states when to prefer this over buy_crypto_price, buy_coin_MX, or any other price sibling. There are no exclusions or prerequisites beyond the payment note, leaving the agent to infer the selection rule from the ticker alone.

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