Skip to main content
Glama

search-repos

Find GitHub repositories by search query, with options to sort by stars, forks, help-wanted issues, or update date and limit results.

Instructions

Search for GitHub repositories

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query
sortNoSort order
limitNoMaximum number of results to return

Implementation Reference

  • The main execution logic for the 'search-repos' tool, using Octokit to query GitHub's search API and format results.
    const searchRepos = async (args: SearchReposArgs) => {
      const { query, sort = "stars", limit = 5 } = args;
      
      try {
        const response = await octokit.rest.search.repos({
          q: query,
          sort,
          per_page: limit,
        });
        
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(
                response.data.items.map(repo => ({
                  name: repo.full_name,
                  description: repo.description,
                  stars: repo.stargazers_count,
                  url: repo.html_url,
                  language: repo.language,
                  forks: repo.forks_count,
                })),
                null,
                2
              ),
            },
          ],
        };
      } catch (error) {
        const errorMessage = error instanceof Error ? error.message : 'Unknown error occurred';
        return {
          content: [
            {
              type: "text",
              text: `Error searching repositories: ${errorMessage}`,
            },
          ],
        };
      }
    };
  • Input schema definition for the 'search-repos' tool, used for listing and validation.
    "search-repos": {
      name: "search-repos",
      description: "Search for GitHub repositories",
      inputSchema: {
        type: "object",
        properties: {
          query: {
            type: "string",
            description: "Search query",
          },
          sort: {
            type: "string",
            enum: ["stars", "forks", "help-wanted-issues", "updated"],
            description: "Sort order",
          },
          limit: {
            type: "number",
            description: "Maximum number of results to return",
          }
        },
        required: ["query"],
      },
    },
  • src/handlers.ts:18-32 (registration)
    MCP server request handlers for listing tools (using 'tools' object) and calling tools (using 'toolHandlers' map).
        // tools
        server.setRequestHandler(ListToolsRequestSchema, async () => ({
            tools: Object.values(tools)
        }));
        server.setRequestHandler(CallToolRequestSchema, async (request) => {
            type ToolHandlerKey = keyof typeof toolHandlers;
            const { name, arguments: params } = request.params ?? {};
            const handler = toolHandlers[name as ToolHandlerKey];
    
            if (!handler) throw new Error("tool not found");
    
            type HandlerParams = Parameters<typeof handler>;
            return handler(params as any);
        })
    }
  • src/tools.ts:322-327 (registration)
    Export of the toolHandlers object mapping tool names to their handler functions, imported and used in handlers.ts.
    export const toolHandlers = {
      "search-repos": searchRepos,
      "get-repo-info": getRepoInfo,
      "list-issues": listIssues,
      "create-issue": createIssue,
    };
  • TypeScript type definition for the input arguments of the searchRepos handler.
    type SearchReposArgs = {
      query: string;
      sort?: "stars" | "forks" | "help-wanted-issues" | "updated";
      limit?: number;
    };
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Search for GitHub repositories' implies a read-only operation but doesn't specify whether it requires authentication, rate limits, pagination behavior, or what the return format looks like. For a search tool with zero annotation coverage, this is a significant gap in transparency.

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 single, efficient sentence with zero waste. It's appropriately sized and front-loaded, immediately conveying the core functionality without unnecessary elaboration.

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 the tool's moderate complexity (3 parameters, no output schema, no annotations), the description is minimally adequate. It states what the tool does but lacks behavioral details and usage context. Without annotations or output schema, the agent must rely heavily on the input schema and external knowledge.

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 already documents all three parameters (query, sort, limit) with descriptions and enum values. The description doesn't add any meaning beyond what the schema provides, such as query syntax examples or limit defaults. Baseline 3 is appropriate when the schema does the heavy lifting.

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

Purpose4/5

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

The description 'Search for GitHub repositories' clearly states the verb ('Search') and resource ('GitHub repositories'), making the tool's purpose immediately understandable. It doesn't specifically differentiate from sibling tools like 'get-repo-info' or 'list-issues', but it's unambiguous about what it does.

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?

The description provides no guidance on when to use this tool versus alternatives like 'get-repo-info' or 'list-issues'. It doesn't mention any prerequisites, exclusions, or specific contexts for usage, leaving the agent to infer based on tool names alone.

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/ualUsham/mcp-github'

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