Skip to main content
Glama
Sign In
Windows Developer MCP Server

Windows Developer MCP Server

by peeyushcodes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

github_search_repos

Search GitHub repositories with query qualifiers, sort by stars, forks, or updated, and limit results.

Instructions

Search GitHub repositories.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "github_search_repos"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoSort field — "stars", "forks", "updated". Default: "stars".stars
limitNoMaximum results (1–30). Default: 10.
orderNoSort order — "asc" or "desc". Default: "desc".desc
queryYesGitHub search query (supports qualifiers like language:python).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/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 of behavioral disclosure. It only states 'Search GitHub repositories' and does not mention rate limits, authentication, sorting, output behavior, or any other operational traits. This leaves the agent guessing about important runtime behavior.

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, concise sentence that immediately communicates the tool's purpose. It is front-loaded, contains no extraneous words, and is appropriately sized for a simple search tool.

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?

The tool has only one required parameter and a full output schema, so the description does not need to explain return values. However, the minimal description leaves gaps about query syntax, rate limit considerations, and when to prefer this tool over siblings, making it adequate but not complete.

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?

The input schema covers all four parameters with clear descriptions (query, sort, order, limit), so the schema already provides high coverage. The description adds no additional parameter semantics beyond what the schema already states, so the baseline score of 3 is appropriate.

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 GitHub repositories' clearly states the tool's action and resource with a specific verb. It distinguishes from similar GitHub tools by focusing on repository search, but does not explicitly mention alternatives, so it lacks direct sibling differentiation.

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 intended usage is implied by the name and description—use it when you need to find GitHub repositories. However, there is no explicit guidance on when to choose this over sibling tools like github_repo_info or github_list_issues, nor any stated exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools