Skip to main content
Glama

Jupiter Quote

jupiter_quote
Read-onlyIdempotent

Best swap route and quote between two Solana token mints via Jupiter Aggregator — expected output amount, price impact, and the route (which AMMs/DEXes it crosses). Amount is in the INPUT token's base units (e.g. lamports for SOL: 1 SOL = 1_000_000_000).

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "amount": "10000000",
      "input_mint": "So11111111111111111111111111111111111111112",
      "output_mint": "Ez1zGM23iZgzxvinkNEnTuSkyicwbahvRjfpRDaWnzbj",
      "slippage_bps": 100
    },
    "name": "jupiter_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesAmount of input_mint to swap, in base units (integer, as a string or number — e.g. "1000000000" for 1 SOL).
input_mintYesInput token mint address (base58).
output_mintYesOutput token mint address (base58).
slippage_bpsNoMax slippage in basis points. Default 50 (0.5%).

Output Schema

NameRequiredDescriptionDefault
routeNo
sourceNo
in_amountNo
swap_modeNo
fetched_atNo
input_mintNo
out_amountNo
output_mintNo
context_slotNo
slippage_bpsNo
swap_usd_valueNo
price_impact_pctNo
other_amount_thresholdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, non-destructive, so safety is covered. The description adds useful behavioral context beyond that: the quote is an aggregation across multiple AMMs/DEXes and the result includes price impact and route, which tells the agent what the aggregation surface looks like. It does not mention quote staleness/expiry or any rate limits, so it stops short of full transparency.

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?

A single front-loaded sentence names the resource, then the returned fields, then the one non-obvious input convention (base units). No filler and no redundant restatement of the tool name.

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 an output schema present and full parameter coverage, the definition covers what an agent needs to invoke it correctly: which mints, how much, in what units, and what the response conveys. The one omission is quote freshness — whether a returned quote is time-sensitive before execution — which matters for a swap-routing tool.

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 all four parameters (including slippage_bps and the base58 mint formats) are already documented in the schema. The description's lamports/base-unit example reinforces the amount semantics but largely restates the schema, and slippage_bps is not mentioned in the description at all. Baseline 3 applies when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Best swap route and quote between two Solana token mints via Jupiter Aggregator') and enumerates what comes back: expected output amount, price impact, and the AMM/DEX route. The quote/route framing clearly separates it from a plain price lookup such as jupiter_price.

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 is implied by the framing — quote before a swap — but the description never says when to call this instead of jupiter_price, nor whether the quote is a pre-trade estimate that must be refreshed. No prerequisites or exclusions are 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.