Skip to main content
Glama
louiscklaw

mcp-github-advanced-search

by louiscklaw

gas_search_code

Search GitHub code by keyword and filename to retrieve matching files with content and links. Get advanced filtered results in JSON format.

Instructions

SEARCH_CODE_EXPLAIN

INTRODUCTION

This is a utilities that search github with advanced filters (e.g. keyword)

the result is in json format with below fields"

[
    {
        "REPOSITORY_LINK": "<repository-found>",
        "FILE_LINK": "<file-found>",
        "RAW_USER_CONTENT_LINK": "<download-link-to-the-file>",
        "FILE_CONTENT": "<downloaded-content>"
    },
    {...},
    {...},
    {...},
    {"next_instructions_md": "<contains-the-instruction-to-get-the-remaining-result>"}
]

when you receive this, please ensure you follow the next_instructions_md to collect all results.

You can use memory, sequential-thinking, structured-argumentation to help solving problems.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordNothe keyword user interested, e.g. `helloworld()` * Please limit the keyword to one single word only (e.g. `helloworld` and not `hello word`) default('')
file_nameNothe file name user interested e.g. `.clinerules` default('')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.2

TDQS

A3.5/5.0
Behavior4/5

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

Annotations are absent, so the description carries the full behavioral burden. It discloses the exact JSON output fields, the presence of next_instructions_md, and the need to follow it for remaining results. This is meaningful behavioral detail, even though auth and rate limits are not mentioned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is cluttered with headings, a large JSON example, and an unrelated suggestion to use memory/sequential-thinking/structured-argumentation. It is structured but not front-loaded and contains non-essential content.

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?

With no output schema, the description usefully provides the response format and next-step instructions. However, it does not explain how gas_search_code relates to sibling tools gas_entrypoint and get_remaining_result, nor does it mention error or edge-case 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 100%, with keyword and file_name already described with examples and constraints. The description adds no additional parameter semantics beyond what the schema provides.

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 the tool searches GitHub with filters (keyword, file_name) and specifies the JSON response shape. It is clear about verb and resource, but it does not explicitly differentiate itself from siblings like gas_entrypoint or get_remaining_result.

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 description implies usage through 'search github with advanced filters' and instructs the agent to follow next_instructions_md to collect all results. However, it lacks explicit guidance on when to prefer this tool over siblings 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.