Skip to main content
Glama

SouthPow crypto & market data

buy_tok_MAG7XON

Paid. Ondo Magnificent 7 and Crypto Portfolio (MAG7XON) 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/MAG7XON.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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 behavioral burden and does well: it discloses that the call is paid ($0.01 USDC on Base or Solana), requires no account or API key, and that failed calls are not charged — material facts for an agent deciding whether to spend. It does not describe response format beyond the three fields, latency, or rate limits, which keeps it short of 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One tight block: payment flag and asset identity are front-loaded, followed by the returned fields, cost/rails, auth requirement, billing guarantee, and endpoint URL. No sentence is filler; each adds a fact the structured fields do not carry (the schema and annotations are empty).

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-annotation, no-output-schema tool, the description supplies what an agent needs: what data comes back, what it costs, how to pay, and that failures are free. What is missing is the concrete response shape (field names/units) and any freshness guarantee for the 'live' price, which would matter for a pricing tool.

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. The description correctly implies no input is needed by advertising 'No account, no API key' and pointing at a fixed URL, so an agent knows the call is fully parameterless.

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 asset (Ondo Magnificent 7 and Crypto Portfolio, ticker MAG7XON) and enumerates the returned data: live USD price, 24h change and market-cap rank. It lacks an explicit verb ('buy' in the name implies purchase, but the text describes a data fetch), which could briefly confuse an agent, though the resource is unambiguous and distinct from every buy_tok_* sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to choose this over alternatives such as buy_crypto_price or buy_coin_* siblings, nor any exclusion criteria. The only decision-relevant context is the price ($0.01) and payment rails, which tells the agent the cost but not the selection condition.

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