Skip to main content
Glama

Jupiter Price

jupiter_price
Read-onlyIdempotent

USD price, 24h change, and aggregated liquidity for one or more Solana token mints, aggregated by Jupiter across every DEX/AMM it indexes (not a single pool — use the dexscreener pack for one specific pool). Up to 50 mints per call.

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": {
      "mints": [
        "So11111111111111111111111111111111111111112",
        "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v",
        "Ez1zGM23iZgzxvinkNEnTuSkyicwbahvRjfpRDaWnzbj"
      ]
    },
    "name": "jupiter_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintsYesSolana token mint addresses (base58), e.g. ["So11111111111111111111111111111111111111112"] for SOL. Max 50.

Output Schema

NameRequiredDescriptionDefault
pricesNo
sourceNo
fetched_atNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds useful context the annotations cannot carry: the data is aggregated across all indexed venues rather than one pool, and calls are capped at 50 mints. It is silent on what happens for unknown/unindexed mints or partial failures, which is a minor gap.

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, no filler, with the scope/aggregation constraint and the sibling alternative front-loaded before the batch limit. Every clause earns its place.

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 a single fully documented parameter, rich annotations, and an output schema handling return shapes, the description is nearly sufficient. The only thing an agent might still want is the behavior on invalid or unindexed mints.

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% — the mints array is documented with base58 format, an example, and min/max items. The description restates 'one or more Solana token mints' and the 50-mint cap, reinforcing but not adding meaning beyond the schema.

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 (price/24h change/liquidity for Solana token mints) and pins down scope: aggregated by Jupiter across every indexed DEX/AMM, not a single pool. An agent can distinguish it from a single-pool price lookup 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 Guidelines4/5

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

Explicitly says to use the dexscreener pack when a single specific pool is wanted, which is a genuine when-not rule, and gives the batching constraint (up to 50 mints). It does not differentiate from the closest sibling, jupiter_quote, leaving the price-vs-quote choice to inference.

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.