Skip to main content
Glama

jupiter_token_info

Get token metadata including verification status, organic score, daily volume, and holder count for a given mint address on Solana.

Instructions

Get detailed token metadata for a specific mint — verification status, organic score, daily volume, holder count.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mintYesToken mint address

Implementation Reference

  • Handler for 'jupiter_token_info' tool: registers with Zod schema (mint string) and calls client.tokenInfo(args.mint).
    register(
      "jupiter_token_info",
      "Get detailed token metadata for a specific mint — verification status, organic score, daily volume, holder count.",
      {
        mint: z.string().describe("Token mint address"),
      },
      async (args) => {
        const result = await client.tokenInfo(args.mint);
        return JSON.stringify(result, null, 2);
      },
    );
  • Registration: registerTokenTools uses the 'register' function to register 'jupiter_token_info' with the MCP server.
    export function registerTokenTools(register: ToolRegistrar, client: JupiterClient) {
      register(
        "jupiter_token_search",
        "Search for Solana tokens by name, symbol, or mint address. Returns metadata, verification status, organic scores, and trading metrics.",
        {
          query: z.string().describe("Token name, symbol, or mint address"),
          limit: z.number().optional().describe("Max results (default 10)"),
        },
        async (args) => {
          const result = await client.tokenSearch(args.query, args.limit);
          return JSON.stringify(result, null, 2);
        },
      );
    
      register(
        "jupiter_token_info",
        "Get detailed token metadata for a specific mint — verification status, organic score, daily volume, holder count.",
        {
          mint: z.string().describe("Token mint address"),
        },
        async (args) => {
          const result = await client.tokenInfo(args.mint);
          return JSON.stringify(result, null, 2);
        },
      );
    }
  • Helper: JupiterClient.tokenInfo(mint) makes a GET request to /tokens/v2/{mint} on the Jupiter API.
    /** Get token metadata and trading metrics by mint */
    async tokenInfo(mint: string) {
      return this.request(`/tokens/v2/${mint}`);
    }
  • src/index.ts:40-58 (registration)
    Generic 'register' wrapper that calls server.tool() for each tool including jupiter_token_info.
    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++;
    }
  • ToolRegistrar type definition used for tool registration functions.
    import type { z } from "zod";
    
    /** Tool registration function — matches McpServer.tool() signature with Zod */
    export type ToolRegistrar = (
      name: string,
      description: string,
      schema: Record<string, z.ZodType>,
      handler: (args: any) => Promise<string>,
    ) => void;
Behavior3/5

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

No annotations provided. Description lists output fields but does not disclose side effects, auth requirements, rate limits, or error behavior. For a read operation, basic transparency is present but incomplete.

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, 15 words, front-loaded with verb and resource. No wasted words. Structure is ideal for quick understanding.

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 low complexity (single param, no output schema) and no annotations, the description lists key output fields. Minor gaps: no error handling or response format details, but sufficient for typical use.

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% with parameter 'mint' described as 'Token mint address'. Description adds the phrase 'for a specific mint' but does not provide additional meaning beyond the schema. Baseline of 3 applies due to high schema coverage.

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 verb 'Get' and the resource 'detailed token metadata' for a specific mint, listing specific fields like verification status, organic score, daily volume, holder count. This distinguishes it from siblings like jupiter_token_search and jupiter_price.

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 guidance on when to use this tool versus alternatives. Does not mention prerequisites, exclusions, or context where this tool is preferred over siblings like jupiter_token_search.

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