Skip to main content
Glama

Best Jupiter swap route for a Solana token pair

solana_quote
Read-only

Best Jupiter swap route for a Solana token pair and an amount: input and output in token units, the minimum received after slippage, price impact, effective price, each route hop and USD values. from and to take a mint address or a symbol such as SOL or USDC; a symbol resolves to the verified token with the highest organic score, and the chosen mint is named. Quote only: nothing is built, signed or sent. Related tools on this server, for a different need: solana_token when you need to check a Solana token: market data and red flags; solana_wallet when you need Solana wallet holdings: SOL and every SPL / Token-2022. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "from": "<from>",
      "to": "<to>",
      "amount": "<amount>"
    },
    "name": "solana_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesMint address or symbol to buy, e.g. USDC
fromYesMint address or symbol to sell, e.g. SOL
amountYesAmount of from in whole tokens, e.g. 1 or 0.25
slippageBpsNoSlippage tolerance in basis points, 0 to 1000 (default 50)

Output Schema

NameRequiredDescriptionDefault
inputNo
notesNo
routeNo
outputNo
sourceNo
checkedAtNo
quoteOnlyNo
disclaimerNo
slippageBpsNo
effectivePriceNo
priceImpactPctNo
symbolResolutionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "checkedAt": {},
      +    "disclaimer": {},
      +    "effectivePrice": {},
      +    "input": {},
      +    "notes": {},
      +    "output": {},
      +    "priceImpactPct": {},
      +    "quoteOnly": {},
      +    "route": {},
      +    "slippageBps": {},
      +    "source": {},
      +    "symbolResolution": {}
      +  },
      +  "type": "object"
      +}
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds genuinely new behavioral context: the quoted fields returned, symbol-resolution behavior (verified token with highest organic score, with the chosen mint named), and the x402 billing model with the explicit note that failed calls are not charged. The cost and failure-charging disclosure is exactly the kind of detail annotations cannot carry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

The core purpose and the quote-only constraint are front-loaded, and each sentence carries information (return fields, resolution rule, alternatives, pricing). The related-tools sentence is long and runs together three distinct tools in one line, which slightly blunts scannability but does not waste words.

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 four-parameter read-only quoting tool with an output schema, this covers everything an agent needs: what is produced, what is not produced (no transaction built or sent), how inputs resolve, which sibling to use otherwise, and the cost model. The enumerated return fields duplicate the output schema slightly but harmlessly.

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?

Schema coverage is 100%, so the baseline would be 3, but the description goes beyond it by explaining that from/to accept either a mint address or a symbol and how a symbol is resolved (verified token with highest organic score, with the resolved mint reported back). SlippageBps semantics are left entirely to the schema, which is the main gap.

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?

The title and first sentence state a specific verb and resource: fetching the best Jupiter swap route for a Solana token pair at a given amount. It also enumerates what the quote contains (minimum received, price impact, effective price, hops, USD values), so an agent can distinguish it from execution or market-data siblings without opening the schema.

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

Usage Guidelines5/5

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

The description explicitly rules out execution ("Quote only: nothing is built, signed or sent") and names two concrete alternatives with the conditions that select them (solana_token for token market data and red flags, solana_wallet for wallet holdings). This is the when/when-not/alternatives pattern the top band requires.

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