Skip to main content
Glama

SouthPow crypto & market data

buy_tok_MNT

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/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 a good job: it discloses the price ($0.05 USDC), accepted payment chains (Base or Solana), that no account or API key is needed, and that failed calls are not billed. That is exactly the kind of commercial/auth context an agent needs before invoking. It omits rate limits, latency, and whether repeated calls within a window are re-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?

The description is front-loaded with the crucial 'Paid.' flag, then the payload, then the payment terms, then the endpoint. Every clause carries distinct information, and there is no filler or repetition of the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter, zero-annotation, output-schema-less tool, the description covers what is returned (USD price, 24h change, market-cap rank), cost, payment rails, auth requirements, and failure billing. An agent has everything needed to decide and invoke correctly.

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 is 4. The description correctly adds nothing spurious about inputs and instead spends its words on the fixed asset and payment mechanics.

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 asset and states exactly what data comes back: 'Mantle (MNT) price: live USD price, 24h change and market-cap rank.' That is a concrete verb-and-resource substitute for a zero-parameter tool. It never references the other price tools in the family (e.g. buy_coin_MNT or buy_crypto_price), so an agent must infer from the tool name alone which sibling to choose among hundreds.

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?

Paid access is signaled up front and the fixed cost is stated, which tells an agent this is a pay-per-call endpoint rather than a free lookup. However, there is no guidance on when to prefer this over buy_crypto_price or buy_coin_MNT, and no exclusions or freshness/caching conditions are given. Usage is implied by the asset name only.

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