Skip to main content
Glama

jupiter_perps_markets

Retrieve perpetual futures markets on Jupiter, including trading pairs, funding rates, and open interest.

Instructions

List Jupiter perpetual futures markets — trading pairs, funding rates, open interest.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for jupiter_perps_markets — calls client.perpsMarkets() and returns JSON-stringified result.
    async () => {
      const result = await client.perpsMarkets();
      return JSON.stringify(result, null, 2);
    },
  • Schema for jupiter_perps_markets — empty object (no parameters needed).
    {},
  • Registration of jupiter_perps_markets tool via the register() helper which delegates to McpServer.tool().
    register(
      "jupiter_perps_markets",
      "List Jupiter perpetual futures markets — trading pairs, funding rates, open interest.",
      {},
      async () => {
        const result = await client.perpsMarkets();
        return JSON.stringify(result, null, 2);
      },
    );
  • JupiterClient.perpsMarkets() — makes GET request to /perps/v1/markets endpoint (WIP).
    async perpsMarkets() {
      return this.request("/perps/v1/markets");
    }
  • src/index.ts:40-57 (registration)
    The register() helper that wraps McpServer.tool() — used as the ToolRegistrar passed to registerPerpsTools.
    function register(
      name: string,
      description: string,
      shape: Record<string, z.ZodType>,
      handler: (args: any) => Promise<string>,
    ) {
      server.tool(name, description, shape, async (args) => {
        try {
          const text = await handler(args);
          return { content: [{ type: "text" as const, text }] };
        } catch (err: any) {
          return {
            content: [{ type: "text" as const, text: `Error: ${err.message}` }],
            isError: true,
          };
        }
      });
      toolCount++;
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It describes a read-only listing operation but does not explicitly state that no mutations occur, or mention any rate limits, permissions, or data freshness. The basic purpose is clear, but deeper behavioral traits are missing.

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 that efficiently communicates the action (list), resource (markets), and key data fields. Every word serves a purpose with no redundancy.

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?

For a simple parameterless listing tool, the description is largely complete. It identifies the three key data fields. However, it lacks information on sorting, pagination, or number of markets, but given the tool's simplicity, this is a minor gap.

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?

The tool has zero parameters with 100% schema coverage (empty schema). The description adds meaning by specifying the returned data includes trading pairs, funding rates, and open interest, which is valuable beyond the empty 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?

The description clearly states the tool lists Jupiter perpetual futures markets with specific data fields (trading pairs, funding rates, open interest). It distinguishes from sibling tools like jupiter_perps_positions, which focus on positions rather than market overview.

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?

No explicit guidance on when to use this tool versus alternatives. The intended use is implied by the description, but there is no mention of when not to use it or alternatives like jupiter_perps_positions for position-specific data.

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