Skip to main content
Glama

AgentFeed

by io.github.seekdaseek
OverviewDiscussionsAdmin

Jupiter DEX quote

get_dex_quote
Read-onlyIdempotent

Solana DEX quote from Jupiter for any SPL pair: output amount, price impact %, the route taken and the slippage assumed. The real executable price on Solana, not an index price. Costs 0.005 USDC per call (x402, USDC on Solana or Base).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountYesamount in raw base units of input mint
input_mintYesinput mint (base58)
output_mintYesoutput mint (base58)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesthe get_dex_quote payload; a real captured example is free at https://x402.ochinimus.app/api/sample/get_dex_quote
toolYesthe tool that produced this payload

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "additionalProperties": {},
+      "description": "the get_dex_quote payload; a real captured example is free at https://x402.ochinimus.app/api/sample/get_dex_quote",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "tool": {
+      "const": "get_dex_quote",
+      "description": "the tool that produced this payload",
+      "type": "string"
+    }
+  },
+  "required": [
+    "tool",
+    "data"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context beyond the annotations by disclosing the per-call cost of 0.005 USDC, the x402 payment mechanism, and the fact that the quote reflects a real executable price rather than an index price.

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 concise and front-loaded: the first sentence states the core purpose and outputs, and the second sentence adds the important cost and network details. Every sentence earns its place, with no filler or repetition of schema content.

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 three-parameter read-only quote tool with full schema coverage and an output schema, this description is complete. It covers what the quote returns, the key distinction from index prices, the cost, and the payment rail, which is everything an agent needs to decide whether and how to invoke the 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 input_mint, output_mint, and amount are already documented with meaningful descriptions such as 'raw base units' and 'base58'. The description reinforces that any SPL pair is supported but does not add substantial parameter-level semantics beyond the schema.

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 clearly identifies the verb-resource pair: retrieving a Solana DEX quote from Jupiter for any SPL pair, and enumerates the key outputs (output amount, price impact, route, slippage). It distinguishes itself from index-price tools by explicitly stating this is the real executable price, though it does not name a specific sibling tool to differentiate from.

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?

The description implies when this tool is appropriate: when an executable on-chain DEX price, rather than an index price, is needed for an SPL pair. However, it provides no explicit when-not-to-use guidance and does not mention alternatives like get_exit_quote or get_spot, leaving the routing decision mostly to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AgentFeed toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources