Skip to main content
Glama

jupiter_portfolio

Retrieve a wallet's complete portfolio across Jupiter DeFi services including swaps, lending, DCA, limit orders, perps, and prediction markets.

Instructions

Get full portfolio for a wallet — all Jupiter positions across swaps, lending, DCA, limit orders, perps, and prediction markets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
walletYesWallet address

Implementation Reference

  • The async handler function that calls client.portfolio(args.wallet) to fetch portfolio data and returns it as JSON string.
    async (args) => {
      const result = await client.portfolio(args.wallet);
      return JSON.stringify(result, null, 2);
    },
  • Zod schema for the tool's input: wallet (string) describing the wallet address to query.
    wallet: z.string().describe("Wallet address"),
  • registerPortfolioTools function that registers the tool with name 'jupiter_portfolio', a description, input schema, and handler callback.
    export function registerPortfolioTools(register: ToolRegistrar, client: JupiterClient) {
      register(
        "jupiter_portfolio",
        "Get full portfolio for a wallet — all Jupiter positions across swaps, lending, DCA, limit orders, perps, and prediction markets.",
        {
          wallet: z.string().describe("Wallet address"),
        },
        async (args) => {
          const result = await client.portfolio(args.wallet);
          return JSON.stringify(result, null, 2);
        },
      );
  • src/index.ts:69-69 (registration)
    Top-level call to registerPortfolioTools(register, client) in the main entry point to wire up the tool.
    registerPortfolioTools(register, client);
  • The JupiterClient.portfolio() method that makes the HTTP GET request to /portfolio/v1/positions with the wallet param.
    async portfolio(wallet: string) {
      return this.request("/portfolio/v1/positions", {
        params: { wallet },
      });
    }
Behavior3/5

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

With no annotations, the description carries the burden. It states it is a retrieval operation but adds no detail on read-only nature, authentication needs, rate limits, or data freshness. Minimal beyond purpose.

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 filler, front-loads the action and scope. Every word contributes to the purpose.

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

Completeness3/5

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

Given no output schema and a single parameter, the description is adequate but lacks detail on the return format, field contents, or potential pagination. Could be more informative for a comprehensive tool.

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?

The schema already covers the 'wallet' parameter with a description. The description adds no additional meaning or usage guidance for the parameter, so baseline 3 applies.

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 uses a specific verb ('Get') and resource ('full portfolio') and explicitly lists the types of Jupiter positions included, which distinguishes it from the many sibling tools that focus on individual operations.

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 implies when to use (when needing a comprehensive overview), but does not provide explicit when-not or alternative tool recommendations. The context of sibling tools partially compensates.

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