Skip to main content
Glama

SouthPow crypto & market data

buy_tok_MAGMA

Paid. Magma Finance (MAGMA) 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/MAGMA.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior2/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 partially meet it: it discloses the $0.05 USDC cost, both accepted chains (Base, Solana), that no account or API key is required, and that failed calls are not charged. These are genuinely valuable disclosures a schema cannot convey. Missing are the cost of a successful call relative to retries, rate limits, and response format, leaving material gaps for a paid endpoint.

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 telegraphic but every clause is load-bearing: payment flag, purpose, exact fields, price, chains, auth model, failure policy and endpoint. It is front-loaded with the paid status before the resource description, which is the right ordering.

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 price lookup, the description covers what data comes back, what it costs, how payment works and that failures are free. The main omission is any statement of response format or freshness/latency guarantees, which matters for a 'live' price claim.

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 arguments are needed and adds nothing misleading about inputs.

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 (Magma Finance / MAGMA) and states the exact payload: live USD price, 24h change and market-cap rank. However, it never distinguishes itself from the near-identical sibling buy_coin_MAGMA or from buy_crypto_price, which an agent would have to disambiguate on its own.

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 when-to-use or when-not-to-use guidance and no mention of the alternative tools that return the same token's price. The payment and auth notes describe mechanics of calling, not the conditions under which this tool should be selected over its 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