Skip to main content
Glama

jupiter_lend_deposit

Create a deposit transaction for Jupiter Lend Earn to earn yield on token assets. Returns a base64-encoded unsigned transaction for signing.

Instructions

Create a deposit transaction for Jupiter Lend Earn. Returns a base64-encoded unsigned transaction to sign and submit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assetYesToken mint address to deposit (e.g. USDC: EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v)
signerYesWallet address making the deposit
amountYesAmount to deposit in base units

Implementation Reference

  • The async handler that calls client.lendDeposit(args) and returns the result as JSON. This is the actual execution logic for the jupiter_lend_deposit tool.
    async (args) => {
      const result = await client.lendDeposit(args);
      return JSON.stringify(result, null, 2);
    },
  • src/tools/lend.ts:5-18 (registration)
    The registerLendTools function registers 'jupiter_lend_deposit' with its description, schema (asset, signer, amount), and handler via the tool registration callback.
    export function registerLendTools(register: ToolRegistrar, client: JupiterClient) {
      register(
        "jupiter_lend_deposit",
        "Create a deposit transaction for Jupiter Lend Earn. Returns a base64-encoded unsigned transaction to sign and submit.",
        {
          asset: z.string().describe("Token mint address to deposit (e.g. USDC: EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v)"),
          signer: z.string().describe("Wallet address making the deposit"),
          amount: z.string().describe("Amount to deposit in base units"),
        },
        async (args) => {
          const result = await client.lendDeposit(args);
          return JSON.stringify(result, null, 2);
        },
      );
  • Zod schema defining the input parameters for jupiter_lend_deposit: asset (string), signer (string), amount (string).
    {
      asset: z.string().describe("Token mint address to deposit (e.g. USDC: EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v)"),
      signer: z.string().describe("Wallet address making the deposit"),
      amount: z.string().describe("Amount to deposit in base units"),
    },
  • The lendDeposit method on JupiterClient that sends a POST request to /lend/v1/earn/deposit with the asset, signer, and amount parameters. This is the underlying API call.
    async lendDeposit(params: { asset: string; signer: string; amount: string }) {
      return this.request("/lend/v1/earn/deposit", {
        method: "POST",
        body: params,
      });
    }
  • src/index.ts:64-69 (registration)
    Top-level registration: registerLendTools(register, client) is called from the main entry point, connecting the lend tools (including jupiter_lend_deposit) to the MCP server.
    registerLendTools(register, client);
    registerTriggerTools(register, client);
    registerRecurringTools(register, client);
    registerPredictionTools(register, client);
    registerPerpsTools(register, client);
    registerPortfolioTools(register, client);
Behavior3/5

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

With no annotations, the description carries the transparency burden. It explains the output (unsigned transaction) implying it's a create-and-sign operation, but does not detail potential side effects, failure modes, or required permissions. This is adequate but not thorough.

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 a concise two-sentence structure. Every word adds value, with no superfluous content. Front-loading the action and output is effective.

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?

Given the tool's simplicity (3 parameters, no output schema), the description covers the core purpose and output. It could mention that the returned transaction needs to be submitted separately, but the overall completeness is high for this use case.

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 the schema itself fully documents the parameters. The description adds no extra semantics beyond what is already in the schema, meeting the baseline expectation.

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 action (Create a deposit transaction), the target (Jupiter Lend Earn), and the output (base64-encoded unsigned transaction). This clearly distinguishes it from siblings like jupiter_lend_withdraw or jupiter_swap_build.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. It does not mention scenarios where other tools would be more appropriate, nor does it provide context about prerequisites or constraints.

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