Skip to main content
Glama

github_search

Search GitHub repositories, users, issues, commits, or authenticated code to gather OSINT evidence and investigate public developer activity.

Instructions

Search GitHub repositories, users, issues or (authenticated) code.

kind: repositories | users | issues | commits | code. Code search requires a GITHUB_TOKEN env var. Keyless requests are rate-limited to ~10/min.

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

Input Schema

NameRequiredDescriptionDefault
kindNorepositories
queryYes
max_resultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.7/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 behavioral burden and usefully discloses that code search requires GITHUB_TOKEN and that keyless requests are rate-limited to ~10/min. It does not explicitly state read-only behavior, pagination, or other operational details an agent may need.

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 short and front-loaded: purpose first, kind values second, authentication/rate-limit constraints third. Each sentence adds useful information without filler.

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 three-parameter search tool with no annotations, no output schema, and zero schema description coverage, the description covers purpose, searchable kinds, and a key auth/rate-limit constraint. It still leaves gaps around query semantics, max_results, and return behavior.

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 0%, so the description must compensate. It usefully enumerates allowed kind values, which the schema does not, but leaves query syntax and max_results behavior unexplained beyond their property names.

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

Purpose5/5

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

The description uses a specific verb and resource: "Search GitHub repositories, users, issues or ... code." It clearly identifies GitHub as the resource, distinguishing it from sibling search tools such as npm_search, web_search, and hackernews_search.

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 domain is clear from "Search GitHub" and the kind values imply appropriate usage for GitHub entities. However, it does not explicitly say when to choose this over sibling search tools or when not to use it.

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