Skip to main content
Glama
TaylorChen

Multi-MCPs

by TaylorChen

search_repositories

Find GitHub repositories by query and language to access code projects through the Multi-MCPs server's unified API integration.

Instructions

Search GitHub repositories

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
languageNo

Implementation Reference

  • The primary handler function for the 'search_repositories' tool. Validates configuration and arguments, then calls the GitHub client's search method.
    async search_repositories(args: Record<string, unknown>) {
      if (!cfg.githubToken) throw new Error("GITHUB_TOKEN is not configured");
      const query = String(args.query || "");
      const language = args.language ? String(args.language) : undefined;
      if (!query) throw new Error("query is required");
      return client.searchRepositories(query, language);
    },
  • Input schema for the tool, specifying 'query' as required string and optional 'language' string.
    inputSchema: {
      type: "object",
      properties: {
        query: { type: "string" },
        language: { type: "string" },
      },
      required: ["query"],
    },
  • Tool registration entry in the GitHub module's registerGitHub() function, including name, description, and schema.
    {
      name: "search_repositories",
      description: "Search GitHub repositories",
      inputSchema: {
        type: "object",
        properties: {
          query: { type: "string" },
          language: { type: "string" },
        },
        required: ["query"],
      },
    },
  • GitHubClient helper method that builds the search query string and performs the API request to GitHub's /search/repositories endpoint.
    searchRepositories(query: string, language?: string) {
      const q = language ? `${query} language:${language}` : query;
      return this.request("/search/repositories", { query: { q } });
    }
  • Invocation of registerGitHub() in the central tools registration function registerAllTools(), which collects tools and handlers from all API modules.
    registerGitHub(),
Behavior1/5

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

No annotations are provided, so the description carries full burden but offers minimal behavioral insight. It doesn't disclose if this is a read-only operation, rate limits, authentication needs, pagination behavior, or what the search returns (e.g., list of repos with basic details). This leaves critical usage aspects unclear.

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 extremely concise with a single, front-loaded sentence that directly states the tool's purpose without unnecessary words. It efficiently communicates the core function, though this brevity contributes to gaps in other dimensions.

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

Completeness2/5

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

Given the complexity (search operation with 2 parameters), lack of annotations, no output schema, and 0% schema coverage, the description is incomplete. It fails to address how results are structured, error conditions, or practical usage details, making it inadequate for effective tool invocation.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate but adds no parameter details. It doesn't explain what 'query' should contain (e.g., keywords, filters) or 'language' (e.g., programming language like 'Python'), leaving both parameters semantically undefined beyond their types.

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

Purpose3/5

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

The description 'Search GitHub repositories' clearly states the action (search) and target resource (GitHub repositories), which is better than a tautology. However, it lacks specificity about what aspects can be searched (e.g., by name, description, topics) and doesn't distinguish from sibling tools like 'search_news' or 'search_photos' beyond the domain.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., authentication), compare to siblings like 'get_repository_info' for detailed info, or specify scenarios where searching is appropriate over other repository-related tools.

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/TaylorChen/muti-mcps'

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