René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"search_code query description teaches incorrect syntax, causing repeated 422 errors","articleBody":"This came out of an analysis of github MCP server errors encountered in my past sessions across 5000 sessions.\n\n**What the agent did**\n\nIn multiple sessions the agent called `search_code` with queries that look reasonable but are rejected with `422 ERROR_TYPE_QUERY_PARSING_FATAL`. Examples from real sessions:\n\n```json\n{\"query\": \"repo:dotnet/runtime \\\"GetAttributes\\\\|SetAttributes\\\" path:System.IO.FileSystem/tests\"}\n{\"query\": \"repo:dotnet/roslyn \\\"ProjectName\\\\|GeneratedFileName\\\\|FilePath\\\" language:csharp file:TestState\"}\n{\"query\": \"repo:dotnet/runtime (review OR agent OR copilot OR AI) path:docs OR path:.github\"}\n{\"query\": \"repo:dotnet/runtime (filename:AGENTS.md OR filename:*review*.md OR filename:*copilot*.md)\"}\n{\"query\": \"--statisticalTest parameter Mann-Whitney repo:dotnet/BenchmarkDotNet\"}\n```\n\n**What went wrong**\n\nEach reflects the agent guessing at syntax that looks plausible but is wrong:\n\n- `\\\"foo\\\\|bar\\\"` — used `\\|` for regex OR inside a quoted string; correct form is `/foo|bar/`\n- `path:docs OR path:.github` — `OR` between qualifier instances without parentheses has surprising precedence\n- `filename:*review*.md` — `filename:` is not a valid qualifier; correct is `path:*review*.md`\n- `--statisticalTest ...` — treated the tool like a shell command\n\n**Why it happens**\n\nThe [current `query` parameter description](https://github.com/github/github-mcp-server/blob/4bded57e02e9346cb1fd595156e07dea51f0fb29/pkg/github/search.go#L176) is:\n\n\u003e \"Search query using GitHub's powerful code search syntax. Examples: `content:Skill language:Java org:github`, `NOT is:archived language:Python OR language:go`, `repo:github/github-mcp-server`. Supports exact matching, language filters, path filters, and more.\"\n\nThis gives the model almost no useful guidance on syntax. It doesn't mention regex (slashes), path globs, `symbol:`, or how boolean operators interact with qualifiers. The example `NOT is:archived language:Python OR language:go` has ambiguous precedence and is likely misread by the model.\n\n**Suggested description**\n\n\u003e Search query using GitHub code search syntax. Qualifiers: repo:owner/repo, org:name, language:Go, path:src/*.js, path:/regex/, symbol:Name, content:term, is:archived|fork. Boolean: AND, OR, NOT, parentheses. Regex: surround with slashes e.g. /sparse.*index/. Glob in path: path:*.ts, path:/src/**/*.js. Examples: 'MyFunc language:go repo:owner/repo', 'symbol:WithContext language:go', '/GetAttributes|SetAttributes/ repo:owner/repo', '(Foo OR Bar) path:src repo:owner/repo'.\n\nThis gives clear and accurate information about the actual syntax without being too verbose. It explicitly names it \"GitHub code search syntax\" which may help the model connect it to the [the documentation page](https://docs.github.com/en/search-github/github-code-search/understanding-github-code-search-syntax) of that title that it has already been trained on.","author":{"url":"https://github.com/danmoseley","@type":"Person","name":"danmoseley"},"datePublished":"2026-04-26T07:27:58.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/2390/github-mcp-server/issues/2390"}