Repository navigation
[mcp-analysis] MCP Structural Analysis - 2026-10-21 #70877
Closed
Replies: 1 comment
|
This discussion has been marked as outdated by GitHub MCP Structural Analysis. A newer discussion is available at Discussion #71128. |
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 11 representative tool calls across 10 GitHub MCP toolsets plus the injected workflow-context block. Ratings remained stable versus the 7-day history (daily average 3.0-3.4/5). The cheapest, most reliable sources continue to be the
workflow_contextblock, themcpscriptswrapper tools (list_workflows,list_label), and explicit-fieldscalls likelist_pull_requests. Thesearch_codetool hit a 429 rate limit again, and four toolsets (issues,discussions,code_security, and onesearchsample) returned responses with their sole result removed by integrity/secrecy policy filtering rather than real data.Key Metrics (Today)
Full Structural Analysis Report
Usefulness Ratings for Agentic Work (Today)
Schema Analysis (Today)
Response Size Analysis (30-Day Toolset Averages)
Tool-by-Tool Analysis (Today)
[[optimization30-Day Trend Summary
Visualizations
Response Size by Toolset
Usefulness Ratings
Daily Token Trend
Size vs Usefulness
Recommendations
list_workflows/list_labelvia themcpscriptswrapper,github_context(zero-cost), andlist_pull_requestswith explicitfields. Prefer these patterns whenever available.issues,discussions,code_security, and one of the twosearchsamples each hit the same failure mode on nearly every sampled day: the single queried item is removed by integrity or secrecy policy filtering before reaching the agent, yielding an empty array instead of real data. This is now a stable systemic gap, not noise, and agents relying on single-item exploratory queries against these toolsets should expect empty results and plan a fallback (broader queries or a different item).search_codehas hit a secondary GitHub rate limit (429) on the majority of sampled days. Treat it as unreliable and fall back tosearch_issues/search_pull_requestswith narrower scope, or add client-side backoff.github_context(66 avg tokens), thelist_workflowswrapper (162 avg tokens), andlist_pull_requests(143 avg tokens) all combine low token cost with 5/5 or near-5/5 ratings.repos/get_file_contents(5,035 avg tokens, driven by full-file reads and one oversized 26,901-token failure on 2026-10-19) andusers/search_users(828 avg tokens, mostly fixed icon/meta overhead) deliver the least value per token. The AGENTS.md large-file guard (pre-check via directory listing before reading) is confirmed as the correct mitigation forrepos; no equivalent mitigation exists yet for thesearch_usersicon/meta overhead since no dedicatedget_usertool is available.All reactions