[mcp-analysis] MCP Structural Analysis - 2026-08-24 #55381
Closed
Replies: 1 comment
|
This discussion has been marked as outdated by GitHub MCP Structural Analysis. A newer discussion is available at Discussion #55764. |
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.
Tested one representative tool per available GitHub MCP toolset against
github/gh-aw(10 tools, ~17,960 tokens total). Average usefulness across all tools: 3.4/5. Best:github_context(5/5, zero-cost identity metadata). Worst:list_issuesandsearch_issues(2/5 each) — both returned empty result sets because the only matching item was redacted by integrity policy, despite well-formed field-filtered queries. The biggest structural finding:list_labelhas no pagination parameter at all and returned all 902 repository labels (~4,900 tokens) in a single call.Note
Data limitation this run:
/tmp/gh-aw/cache-memory/was mounted read-only in this session, so no historical data could be loaded or persisted — this report reflects a single-day snapshot only, not a 30-day trend. Amissing_datasignal was raised for this.Full Structural Analysis Report
Executive Summary
github_context: 5/5list_issues/search_issues: 2/5Usefulness Ratings for Agentic Work
Schema Analysis
Response Size Analysis
Tool-by-Tool Analysis
30-Day Trend Summary
Not available this run —
/tmp/gh-aw/cache-memory/mcp_analysis.jsonlcould not be read or written because the cache-memory mount was read-only in this session. Only today's snapshot (2026-08-24, 10 data points) is reflected above.Recommendations
get_label,list_pull_requests,list_workflows(mcpscripts wrapper),list_discussions, and the injectedgithub_contextblock — prefer these first when their data suffices.list_labelshould supportperPage/page— a repo with hundreds of labels currently forces a single oversized response.list_code_scanning_alertsand similar rule-based tools could omit the fullrule.helptutorial after the first occurrence of a given rule ID to cut duplicate payload.get_label(90 tokens),list_workflowsvia mcpscripts (220 tokens),list_pull_requests(320 tokens).get_file_contentson README.md (8,100 tokens, dominated by repo content, not protocol overhead) and unboundedlist_label(4,900 tokens for 902 labels).list_issuesandsearch_issuesreturned zero usable rows this run because their only matching item was filtered by integrity policy. This isn't a schema/size problem, but agents relying on these tools should expect occasional silent gaps and not assume an empty array means "no matching issues exist."Visualizations
Response Size by Toolset
Usefulness Ratings
Size vs Usefulness
References: §32724667110
All reactions