Skip to main content
Glama
0xjcf
by 0xjcf

search-code

Search for code patterns within repositories using queries and file filters to locate specific implementations or functions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query to find code in the repository
filePatternNoOptional file pattern to limit search (e.g., '*.ts')
maxResultsNoMaximum number of results to return

Implementation Reference

  • The handler function for the 'search-code' tool. It constructs a grep command to search the 'src' directory for the query (optionally filtered by file pattern), limits results, parses the output into file, line number, and content matches, formats a success response, and returns it as text content. Handles no-results and errors gracefully.
    async ({ query, filePattern, maxResults }) => {
      try {
        const searchPattern = filePattern ? `--include="${filePattern}"` : "";
        const command = `grep -n ${searchPattern} -r "${query}" src --color=never | head -n ${maxResults}`;
    
        let results;
        try {
          results = execSync(command, { encoding: "utf-8" });
        } catch (error) {
          // grep returns non-zero exit code when no results found
          results = "";
        }
    
        const matches = results
          .split("\n")
          .filter((line) => line.trim().length > 0)
          .map((line) => {
            const [file, lineNum, ...contentParts] = line.split(":");
            const content = contentParts.join(":").trim();
            return { file, lineNum: parseInt(lineNum, 10), content };
          });
    
        const result = createSuccessResponse(
          {
            query,
            filePattern: filePattern || "all files",
            resultsCount: matches.length,
            matches,
          },
          "search-code"
        );
    
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(result, null, 2),
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(
                createErrorResponse(
                  error instanceof Error ? error.message : String(error),
                  "search-code"
                ),
                null,
                2
              ),
            },
          ],
          isError: true,
        };
      }
    }
  • Zod schema defining the input parameters for the 'search-code' tool: query (required string), optional filePattern (string glob), and maxResults (number, default 10).
    {
      query: z.string().describe("Search query to find code in the repository"),
      filePattern: z
        .string()
        .optional()
        .describe("Optional file pattern to limit search (e.g., '*.ts')"),
      maxResults: z
        .number()
        .default(10)
        .describe("Maximum number of results to return"),
    },
  • The server.tool call that registers the 'search-code' tool, including its name, input schema, and handler function.
    server.tool(
      "search-code",
      {
        query: z.string().describe("Search query to find code in the repository"),
        filePattern: z
          .string()
          .optional()
          .describe("Optional file pattern to limit search (e.g., '*.ts')"),
        maxResults: z
          .number()
          .default(10)
          .describe("Maximum number of results to return"),
      },
      async ({ query, filePattern, maxResults }) => {
        try {
          const searchPattern = filePattern ? `--include="${filePattern}"` : "";
          const command = `grep -n ${searchPattern} -r "${query}" src --color=never | head -n ${maxResults}`;
    
          let results;
          try {
            results = execSync(command, { encoding: "utf-8" });
          } catch (error) {
            // grep returns non-zero exit code when no results found
            results = "";
          }
    
          const matches = results
            .split("\n")
            .filter((line) => line.trim().length > 0)
            .map((line) => {
              const [file, lineNum, ...contentParts] = line.split(":");
              const content = contentParts.join(":").trim();
              return { file, lineNum: parseInt(lineNum, 10), content };
            });
    
          const result = createSuccessResponse(
            {
              query,
              filePattern: filePattern || "all files",
              resultsCount: matches.length,
              matches,
            },
            "search-code"
          );
    
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(result, null, 2),
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(
                  createErrorResponse(
                    error instanceof Error ? error.message : String(error),
                    "search-code"
                  ),
                  null,
                  2
                ),
              },
            ],
            isError: true,
          };
        }
      }
    );
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/0xjcf/MCP_CodeAnalysis'

If you have feedback or need assistance with the MCP directory API, please join our Discord server