[mcp-analysis] MCP Structural Analysis - 2026-09-14 #60828
Closed
Replies: 1 comment
|
This discussion has been marked as outdated by GitHub MCP Structural Analysis. A newer discussion is available at Discussion #61129. |
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.
Analyzed 10 representative GitHub MCP tools (one per toolset) for token cost and schema quality. Today's calls totaled 22,902 tokens at an average usefulness of 3.2/5. Best:
github_context(workflow-injected, 5/5, 80 tokens). Worst:search_code(1/5) — hit a 429 rate limit with no retry. Recurring pattern across 14 measured days: a fixed_meta.serverInfoicon block inflates every non-wrapper tool's payload regardless of actual content size, while themcpscriptswrapper (list_workflows) stays clean.Full Structural Analysis Report
Executive Summary
github_context(5/5, 80 tokens)search_code(1/5, rate-limited)Usefulness Ratings
github_contextlist_workflowslist_code_scanning_alertslist_discussionslist_pull_requestslist_issuessearch_usersget_labelget_file_contentssearch_codeSchema Analysis
github_contextlist_workflowslist_code_scanning_alertslist_discussionslist_pull_requestslist_issuessearch_usersget_labelget_file_contentssearch_codeResponse Size Analysis (All-Time Avg by Toolset)
Tool-by-Tool Analysis
github_contextlist_workflowsmcpscriptswrapper returns clean JSON with explicit pagination metadata and zero icon bloat — consistent for 14 days.list_code_scanning_alertsmessage.list_discussions_metablock dominates aperPage=1payload.list_pull_requestsfieldsparam is the single biggest size lever.list_issuessearch_usersget_label_metaicon block — per-call overhead dominates.get_file_contentssearch_code30-Day Trend Summary
Rating dipped today mainly because
list_issues/list_pull_requestswere called without field filters (recovering that filter would push both back to their usual 4-5 range) andsearch_codefailed on rate limit.Visualizations
Recommendations
High-value tools (4-5 rating):
github_context(free identity source, always prefer overget_me),list_workflowsvia themcpscriptswrapper (clean schema, explicit pagination — use--perPageover the built-in tool),list_code_scanning_alerts(actionable CodeQL detail, worth the token cost givenstate:open,severity:critical,highfiltering).Tools needing improvement:
search_codeneeds client-side backoff/retry — it has the highest call-to-call reliability variance of any tool tested (2 of last 4 runs failed on 429).get_file_contentscost is highly target-dependent and unbounded for auto-appended files (e.g. contributor lists) — prefer range/line-limited reads where supported.Context-efficient tools:
github_context,list_workflows,list_issues/list_pull_requests(when field-filtered — omittingbodyrecovers ~90% of the token cost seen today).Context-heavy tools:
get_file_contents(11,900 tokens, growing),list_code_scanning_alerts(7,200 tokens, inherent to multi-alert detail), both dominated less by schema depth than by the size of the underlying content being returned.Cross-cutting fix: every non-wrapper GitHub MCP tool repeats a fixed
_meta.serverInfoicon block (base64) on every response — for small-payload tools (get_label,list_discussions,search_users) this overhead is a significant fraction of total tokens. Suppressing_metawhere not needed would be the single highest-leverage schema improvement available.References:
Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
api.anthropic.comTo allow these domains, add them to the
network.allowedlist in your workflow frontmatter:See Network Configuration for more information.
All reactions