Repository navigation
[mcp-analysis] MCP Structural Analysis - 2026-10-22 #71128
Closed
Replies: 1 comment
|
This discussion has been marked as outdated by GitHub MCP Structural Analysis. A newer discussion is available at Discussion #71433. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Daily structural analysis of the GitHub MCP server: 11 tools sampled across 9 toolsets today, plus the zero-cost
<github-context>identity block. Average usefulness 3.2/5. Best:github_context,list_pull_requests,list_label,list_workflows(all 5/5). Worst:search_code(1/5, hit a 429 rate limit again). The dominant pattern across all 9 sampled days: mcpscripts wrappers and explicitfieldsselection consistently beat built-in tools' default payloads, which are padded with a fixed ~3.4KB icon/_metablock regardless of content size.Full Structural Analysis Report
Executive Summary
github_context,list_pull_requests*,list_label,list_workflows: 5/5search_code: 1/5*
list_pull_requestsrated 4/5 today pending full star table below; see per-tool table.Usefulness Ratings for Agentic Work (Today)
github_contextlist_pull_requestsfieldslist_label(mcpscripts)list_workflows(mcpscripts)get_file_contentssearch_issueslist_issueslist_code_scanning_alertslist_discussionssearch_userssearch_codeSchema Analysis
github_contextget_file_contentslist_issueslist_pull_requestslist_code_scanning_alertslist_discussionssearch_userssearch_codesearch_issueslist_label(mcpscripts)list_workflows(mcpscripts)Response Size Analysis (Today)
Tool-by-Tool Analysis
30-Day Trend Summary
github_context,list_pull_requests,list_label,list_workflowslist_issues,list_code_scanning_alerts,list_discussions— policy/secrecy filtering of the sole sampled item is now a stable systemic pattern, not noisesearch_codehits secondary rate limits (429) on the majority of sampled days30-day average tokens by tool (lower is better for context budget):
Recommendations
github_context(free),list_pull_requestswith explicitfields, and themcpscriptswrappers forlist_label/list_workflows— all avoid the icon/_metaoverhead that the built-in GitHub MCP server attaches to every response.search_usersandget_label(built-in) carry a fixed ~2.4–3.4KB icon/_metablock regardless of payload size — afields/minimal-metadata mode would meaningfully cut token cost.search_codeneeds a documented retry/backoff story for its recurring secondary rate limit.github_context,list_pull_requests,list_label,list_workflows— use these patterns (explicitfields, mcpscripts wrappers) as the template for other list endpoints.get_file_contents(full-file reads bring fixed overhead plus duplicated body content incontent[]andstructuredContent),search_users/search_code(icon/_meta bloat). Always pre-check file size via a directory listing before reading, and always passperPageon search calls — omitting it today causedsearch_issuesto return ~30 items instead of the intended single-item sample.Visualizations
Response Size by Toolset
Usefulness Ratings
Daily Token Trend
Size vs Usefulness
All reactions