Skip to main content
Glama

jupiter_limit_order_cancel

Cancel one or more open limit orders on Jupiter by specifying the maker wallet and order public keys. Manage your DeFi orders directly on Solana.

Instructions

Cancel one or more open limit orders.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
makerYesWallet that created the orders
ordersYesOrder public keys to cancel

Implementation Reference

  • Tool handler for jupiter_limit_order_cancel. Accepts maker wallet and array of order public keys, calls client.triggerCancel (POST /trigger/v2/orders/cancel), and returns JSON result.
    register(
      "jupiter_limit_order_cancel",
      "Cancel one or more open limit orders.",
      {
        maker: z.string().describe("Wallet that created the orders"),
        orders: z.array(z.string()).describe("Order public keys to cancel"),
      },
      async (args) => {
        const result = await client.triggerCancel(args);
        return JSON.stringify(result, null, 2);
      },
    );
  • Zod schema defining the input parameters: maker (string) and orders (array of strings).
    {
      maker: z.string().describe("Wallet that created the orders"),
      orders: z.array(z.string()).describe("Order public keys to cancel"),
    },
  • src/index.ts:46-57 (registration)
    Generic MCP registration via McpServer.tool(), invoked by the register function. The tool name 'jupiter_limit_order_cancel' is passed to this from trigger.ts via registerTriggerTools.
    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++;
  • JupiterClient.triggerCancel — makes a POST request to /trigger/v2/orders/cancel with the maker and orders array to cancel limit orders.
    async triggerCancel(params: { maker: string; orders: string[] }) {
      return this.request("/trigger/v2/orders/cancel", {
        method: "POST",
        body: params,
      });
    }
Behavior2/5

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

No annotations provided. Description does not disclose side effects (e.g., irreversible), partial success, or auth requirements. Minimal behavioral info beyond the basic action.

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?

Single sentence, no fluff. Front-loaded with verb and resource.

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?

No output schema or description of return value. Lacks info on error handling, idempotency, or success indicators. For a tool with no annotations, more context needed.

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%, so description adds no extra meaning. Repeats order public keys but no additional detail on format or constraints.

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?

Description uses specific verb 'cancel' and resource 'open limit orders'. Clearly distinguishes from sibling tools like 'jupiter_limit_order_create' (create) and 'jupiter_limit_orders' (list).

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 cancel vs modify or other alternatives. For a simple tool, the context is implied but not stated.

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