Repository navigation
[mcp-analysis] MCP Structural Analysis - 2026-10-08 #66871
Closed
Replies: 1 comment
|
This discussion has been marked as outdated by GitHub MCP Structural Analysis. A newer discussion is available at Discussion #67192. |
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 10 representative GitHub MCP tool calls across 9 toolsets plus the injected workflow-context block. Today's calls totaled 3,794 tokens at an average usefulness of 3.0/5 — best was
github_context(5/5, zero MCP overhead) and worst wassearch_code(1/5, hit a secondary rate limit on the very first attempt, the third such hit in four runs).Key Findings
list_issuesandlist_code_scanning_alertsboth returned a clean empty array while silently withholding real items (1 issue, 5 alerts) behind an "approved integrity" gate. An agent cannot tell "nothing found" from "results hidden" — this is worse for agentic reliability than any token-bloat problem._metais a persistent, avoidable tax on every single-item/search call (get_label,search_users,search_code,list_discussions) — consistently 60-85% of response bytes across all 4 days, with zero payload value.fields-filtered root directory listing (770 tokens) correctly surfaced thatREADME.mdis 49.7KB before any full-file read was attempted, avoiding the overflow failures seen on 2026-10-05 and 2026-10-07.list_workflowswrapper remains the cleanest pagination example — honorsperPage, returns a tight envelope withtotal_count, and carries no icon-metadata bloat (plain CLI JSON passthrough).Full Structural Analysis Report
Executive Summary
github_context: 5/5search_code: 1/5Usefulness Ratings for Agentic Work
github_contextlist_pull_requestsget_file_contentslist_workflowslist_discussionslist_issueslist_code_scanning_alertsget_labelsearch_usersget_usercallsearch_codeSchema Analysis
github_contextget_file_contentslist_issueslist_pull_requestslist_code_scanning_alertslist_discussionsget_labelsearch_userssearch_codelist_workflowsResponse Size Analysis (all-time toolset averages, 4 days)
Note:
code_securityandreposaverages are skewed by two outlier full-text failures (33.7k-token alert dump on 2026-10-06, 13.2k-token README overflow on 2026-10-07) — the large-file guard applied today kept both toolsets well-behaved.Tool-by-Tool Analysis (today, 2026-10-08)
github_contextlist_pull_requestsget_file_contentslist_workflowslist_discussionslist_issueslist_code_scanning_alertsget_labelsearch_userssearch_code30-Day Trend Summary
Recommendations
github_context,list_pull_requests,get_file_contents(when paired with field-filtered directory pre-check),list_workflows(via mcpscripts wrapper).list_issuesandlist_code_scanning_alerts— both now routinely mask real data behind integrity-policy filtering with no visible count of what was withheld;search_code— needs backoff/retry handling at the caller or server level given 3 rate-limit hits in 4 runs.github_context(61 tok, 5★),list_pull_requests(75 tok, 5★),list_workflows(172 tok, 4★).code_securityandreposwhen the large-file guard isn't applied — both stayed small today specifically because the directory-listing-first pattern was used before any full-content read.Visualizations
Response Size by Toolset
Usefulness Ratings
Daily Token Trend
Size vs Usefulness
All reactions