Skip to main content
Glama

Github

by io.github.pipeworx-io

Search Repos

search_repos
Read-onlyIdempotent

Search GitHub repositories by keyword. Returns repo name, description, star count, forks, primary language, and URL. Use when exploring projects or finding code implementations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort results by: stars, forks, or updated (default: stars)
queryYesSearch query string (e.g., "react hooks", "cli tool language:go")
per_pageNoNumber of results to return (default 10, max 30)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
reposYesList of matching repositories
total_countYesTotal number of matching repositories
incomplete_resultsYesWhether the results are incomplete

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "incomplete_results": {
+      "description": "Whether the results are incomplete",
+      "type": "boolean"
+    },
+    "repos": {
+      "description": "List of matching repositories",
+      "items": {
+        "properties": {
+          "description": {
+            "description": "Repository description",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "forks": {
+            "description": "Number of forks",
+            "type": "number"
+          },
+          "full_name": {
+            "description": "Full repository name (owner/repo)",
+            "type": "string"
+          },
+          "language": {
+            "description": "Primary programming language",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "name": {
+            "description": "Repository name",
+            "type": "string"
+          },
+          "open_issues": {
+            "description": "Number of open issues",
+            "type": "number"
+          },
+          "stars": {
+            "description": "Number of stargazers",
+            "type": "number"
+          },
+          "topics": {
+            "description": "Repository topics/tags",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "updated_at": {
+            "description": "Last update timestamp",
+            "type": "string"
+          },
+          "url": {
+            "description": "Repository URL",
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "full_name",
+          "description",
+          "stars",
+          "forks",
+          "language",
+          "url",
+          "topics",
+          "updated_at",
+          "open_issues"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total_count": {
+      "description": "Total number of matching repositories",
+      "type": "number"
+    }
+  },
+  "required": [
+    "total_count",
+    "incomplete_results",
+    "repos"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "react hooks"
+  },
+  {
+    "per_page": 20,
+    "query": "cli tool language:go",
+    "sort": "stars"
+  }
+]
  3. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false). The description adds no new behavioral context such as rate limits, authentication needs, or pagination behavior; it only repeats return fields which are likely in the output schema. No contradiction arises.

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 exactly two sentences, front-loaded with the main action and resource. It includes the return fields and a usage hint without unnecessary fluff. Every sentence earns its place.

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

Completeness5/5

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

Given the simple tool, complete schema coverage, presence of an output schema, and strong annotations, the description provides the essential context for an agent to select and invoke the tool. The usage hint adds extra value beyond the structured data.

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%. The schema already provides detailed descriptions and examples for query, sort, and per_page. The description does not add any extra meaning or clarification beyond what the schema offers, so it stays at the baseline.

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 the specific verb 'Search' with the resource 'GitHub repositories' and specifies the search scope 'by keyword.' It clearly distinguishes from sibling tools like search_code (which searches code content) and get_repo (which fetches a single repo).

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?

The description explicitly states when to use this tool: 'Use when exploring projects or finding code implementations.' This provides clear usage context. It does not mention when not to use it or alternatives, so it misses the full 'when/when-not/alternatives' guidance.

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

All Github toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation4/5

Most tools target distinct purposes (e.g., ask_pipeworx vs. get_repo vs. validate_claim), but there is some overlap between ask_pipeworx and ask_pipeworx_grounded, and between bet_research and polymarket_edges. Overall, an agent can generally distinguish them.

Naming Consistency2/5

Tool names lack a consistent pattern: some are verb_noun (search_repos, get_user), others are noun_verb (entity_profile), and many are compound descriptor phrases (polymarket_arbitrage, scan_dependency). This mixed convention makes the set feel disjointed.

Tool Count2/5

38 tools is excessive for a server named 'Github', especially since many tools (e.g., ai_visibility_check, bet_research) are unrelated to GitHub functionality. The count would be appropriate for a broader 'Pipeworx' server but not for a focused GitHub server.

Completeness2/5

The GitHub-relevant tools are limited to read-only operations (get_repo, list_commits, etc.), lacking essential actions like creating/updating repos, issues, or pull requests. The inclusion of numerous non-GitHub tools does not compensate for these gaps.

Resources