Skip to main content
Glama

ArcanumFleet Jupiter Swap Quote

arcanum_jupiter_quote
Read-onlyIdempotent

Use this to fetch a live Jupiter swap quote, expected output amount, price impact percentage, and route hop count between two Solana SPL mints. Costs 0.002 USDC via x402.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "output_mint": "<output_mint>",
      "amount": "<amount>"
    },
    "name": "arcanum_jupiter_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesInput amount in atomic units (lamports)
input_mintNoInput SPL mint address (defaults to wrapped SOL)
output_mintYesOutput SPL mint address

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / amount / description
      Previous value: -"Amount in atomic units (lamports)"New value: +"Input amount in atomic units (lamports)"
    • changedInput schema / properties / input_mint / description
      Previous value: -"Input SPL mint (default: SOL)"New value: +"Input SPL mint address (defaults to wrapped SOL)"
    • changedInput schema / properties / output_mint / description
      Previous value: -"Output SPL mint"New value: +"Output SPL mint address"
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, openWorld and idempotent, so most of the safety profile is covered. The description contributes genuinely new behavior: the call is metered and costs 0.002 USDC via x402, which an agent must know before invoking. It omits quote staleness/expiry semantics, which keeps it below 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?

Two sentences, zero filler, and the capability statement is front-loaded ahead of the payment caveat. Every clause carries information an agent needs.

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?

With no output schema, the description usefully names the returned fields (output amount, price impact, route hop count), and it discloses the payment model for a three-parameter, read-only tool. Missing are output-format specifics and whether quotes expire, which are minor for a quote endpoint.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so amount units, input_mint defaulting to wrapped SOL, and output_mint are all already documented in the schema. The description only restates that the quote spans 'two Solana SPL mints' and adds no format or constraint detail beyond the structured fields, so the baseline 3 applies.

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?

States a specific verb ('fetch') and resource ('live Jupiter swap quote') and even enumerates the returned fields (output amount, price impact, route hop count). It does not explicitly contrast itself with any sibling, so it stops short of the top score, but the purpose is unmistakable.

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?

'Use this to fetch a live Jupiter swap quote' implies the usage context, and the cost note hints it should be called deliberately rather than in bulk. There is no explicit when-not guidance, no mention of what to call instead for related tasks like liquidity checking, and no prerequisites stated.

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