Skip to main content
Glama

jupiter_token_search

Search Solana tokens by name, symbol, or address to get metadata, verification status, and trading metrics.

Instructions

Search for Solana tokens by name, symbol, or mint address. Returns metadata, verification status, organic scores, and trading metrics.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesToken name, symbol, or mint address
limitNoMax results (default 10)

Implementation Reference

  • The registerTokenTools function registers the 'jupiter_token_search' tool with its schema and handler.
    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);
        },
      );
    }
  • The async handler that calls client.tokenSearch() and returns the JSON result.
    async (args) => {
      const result = await client.tokenSearch(args.query, args.limit);
      return JSON.stringify(result, null, 2);
    },
  • Input schema for the tool: query (required string) and limit (optional number).
    {
      query: z.string().describe("Token name, symbol, or mint address"),
      limit: z.number().optional().describe("Max results (default 10)"),
    },
  • The JupiterClient.tokenSearch() method that calls the /tokens/v2/search API endpoint.
    async tokenSearch(query: string, limit?: number) {
      return this.request("/tokens/v2/search", {
        params: { query, limit },
      });
    }
  • src/index.ts:40-58 (registration)
    The generic register() function that wraps McpServer.tool() with error handling, used to register all tools including jupiter_token_search.
    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++;
    }
Behavior3/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 indicates a read operation ('Search') and lists return fields, but does not disclose data freshness, authentication needs, or error behavior. Without annotations, 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that efficiently conveys purpose and output. It is compact but could benefit from structured formatting (e.g., bullets) to improve readability for complex response expectations.

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 no output schema, the description adequately lists the types of returned data (metadata, verification, scores, metrics). It is missing details on sorting, pagination, and error handling, but covers key aspects of the tool's output.

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 descriptions for 'query' and 'limit' already explaining they accept name/symbol/mint and max results. The description largely repeats this, adding little new semantic value beyond what the schema provides.

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 searches for Solana tokens by name, symbol, or mint address, and returns metadata, verification status, organic scores, and trading metrics. This distinguishes it from siblings like jupiter_token_info 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?

The description implies use for finding tokens, but does not explicitly state when to use this tool over alternatives like jupiter_token_info (for detailed info by address) or jupiter_price (for price). No exclusions or prerequisites are mentioned.

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