Skip to main content
Glama

jupiter_price

Get current USD prices for Solana tokens by passing comma-separated mint addresses. Optionally include confidence, depth, and last swap time.

Instructions

Get current USD prices for one or more Solana tokens. Pass mint addresses comma-separated.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mintsYesComma-separated mint addresses
showExtraInfoNoInclude confidence, depth, and last swap time

Implementation Reference

  • The 'registerPriceTools' function registers the 'jupiter_price' tool with the MCP server. The handler (lines 13-17) splits comma-separated mint addresses and calls `client.price()` to fetch USD prices from Jupiter API.
    export function registerPriceTools(register: ToolRegistrar, client: JupiterClient) {
      register(
        "jupiter_price",
        "Get current USD prices for one or more Solana tokens. Pass mint addresses comma-separated.",
        {
          mints: z.string().describe("Comma-separated mint addresses"),
          showExtraInfo: z.boolean().optional().describe("Include confidence, depth, and last swap time"),
        },
        async (args) => {
          const ids = args.mints.split(",").map((s: string) => s.trim());
          const result = await client.price(ids, args.showExtraInfo);
          return JSON.stringify(result, null, 2);
        },
      );
  • Zod schema for 'jupiter_price': `mints` (required string, comma-separated addresses) and `showExtraInfo` (optional boolean for confidence/depth/swap time).
    {
      mints: z.string().describe("Comma-separated mint addresses"),
      showExtraInfo: z.boolean().optional().describe("Include confidence, depth, and last swap time"),
    },
  • src/index.ts:63-69 (registration)
    The 'jupiter_price' tool is registered by calling `registerPriceTools(register, client)` in the main entry point.
    registerPriceTools(register, client);
    registerLendTools(register, client);
    registerTriggerTools(register, client);
    registerRecurringTools(register, client);
    registerPredictionTools(register, client);
    registerPerpsTools(register, client);
    registerPortfolioTools(register, client);
  • The `price()` method on JupiterClient sends a GET request to `/price/v3` with comma-joined mint IDs and optional `showExtraInfo` parameter.
    async price(ids: string[], showExtraInfo?: boolean) {
      return this.request("/price/v3", {
        params: {
          ids: ids.join(","),
          showExtraInfo: showExtraInfo ? "true" : undefined,
        },
      });
    }
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It only says 'Get current USD prices' without addressing staleness, rate limits, or error behavior. This is insufficient for a price API.

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 with no waste. The essential action and input format are front-loaded. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool lacks an output schema and annotations, so the description should compensate by explaining return format or common error cases. It does not, leaving the agent guessing about the response structure.

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 coverage is 100% and both parameters are described in the schema. The description adds no new semantic meaning beyond reinforcing the comma-separated format, which is already in the schema. Baseline 3 is appropriate.

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 description clearly states the tool gets current USD prices for Solana tokens, using a specific verb and resource. It distinguishes itself from sibling tools like jupiter_swap or jupiter_portfolio, which have different purposes.

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 provides basic usage instructions ('Pass mint addresses comma-separated') but does not explain when to prefer this tool over alternatives like jupiter_token_info, nor does it mention any exclusions or prerequisites.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ExpertVagabond/jupiter-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server