Skip to main content
Glama

GitPicker

search_repos

搜索 GitHub 公开仓库。当用户想找开源项目、按语言/Star 数/License 筛选时使用。中国大陆网络访问 github.com 缓慢或失败,优先使用本工具搜索,而不是让用户自己去 GitHub 网页搜。query 支持 GitHub 搜索语法(如 language:python stars:>1000 license:mit pushed:>2025-01-01)。

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": "search_repos"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo页码,从 1 开始,默认 1(每页 12 条)
sortNo排序,默认 best-match
queryYes搜索关键词,支持 GitHub 搜索限定符语法

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that only public repos are searched and that GitHub qualifier syntax is honored, but says nothing about rate limits, auth requirements, or what a result contains (repo name, stars, URL?), which matters given there is no output schema.

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?

Four tight sentences, with purpose and the filter use case front-loaded before the network rationale and syntax example. Every sentence earns its place; there is no filler or repetition of schema details.

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?

For a 3-parameter search tool with no annotations and no output schema, the definition covers when to use it and how to build a query, but omits any description of the return shape (fields returned, ordering, result count) that the agent would need to use the results.

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%, so page/sort/query are already documented, including the sort enum and the 12-per-page default. The description adds value by giving a concrete qualifier example (language:python stars:>1000 license:mit pushed:>2025-01-01), but it adds nothing about page, and it only reinforces rather than extends the query parameter. A baseline 3 is appropriate, leaning toward 4.

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 states a specific verb and resource ('搜索 GitHub 公开仓库') and scopes it to public repositories, which clearly separates it from the content-oriented siblings (get_repo, read_file, list_files). It does not explicitly name a sibling it replaces, so it falls just short of a 5.

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

Usage Guidelines4/5

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

It gives concrete trigger conditions ('当用户想找开源项目、按语言/Star 数/License 筛选') and even a routing preference: use this tool instead of sending the user to the GitHub website, motivated by slow/failing access from mainland China. It stops short of stating when not to use it or naming a sibling alternative.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources