[mcp-analysis] MCP Structural Analysis - 2026-08-28 #56642
Closed
Replies: 1 comment
|
This discussion was automatically closed because it expired on 2026-08-29T16:04:41.409Z.
|
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 GitHub MCP tool responses across 9 toolsets plus the injected workflow-context block. 10 data points collected today (2026-08-28), 40 total across the 4-day rolling window. Average usefulness held steady at 3.6/5. Best:
github_contextandlist_workflows(mcpscripts wrapper), both 5/5. Worst:list_issues(2/5) — a fourth consecutive day where one issue is silently redacted by an integrity policy filter with no visible content, which continues to block agents from assessing it. The clearest recurring pattern: several non-wrapper tools (get_label,list_discussions,search_users,search_code,get_file_contents) pay a fixed ~550-token base64 icon_meta.serverInfooverhead on every call, which can exceed the size of the actual payload for small lookups.Full Structural Analysis Report
Executive Summary
github_context/list_workflows: 5/5list_issues: 2/5Usefulness Ratings for Agentic Work
github_contextlist_workflows(mcpscripts)list_code_scanning_alertslist_pull_requestssearch_codeget_file_contentsget_labellist_discussionssearch_userslist_issuesSchema Analysis
github_contextlist_workflowslist_code_scanning_alertslist_pull_requestssearch_codeget_file_contentsget_labellist_discussionssearch_userslist_issuesResponse Size Analysis
Tool-by-Tool Analysis (Today, 2026-08-28)
github_contextlist_workflowslist_code_scanning_alertslist_pull_requestssearch_codeget_file_contentsget_labellist_discussionssearch_userslist_issues30-Day Trend Summary
Recommendations
github_context(free),list_workflowsvia the mcpscripts wrapper,list_pull_requests,list_code_scanning_alerts,search_code— prefer these when the schema fits the task.list_issues— the integrity-policy redaction has now recurred for 4 consecutive days with zero visible content, and should either surface a summarized/sanitized view or a clearer signal of what triggered the filter.github_context,list_workflows,list_pull_requests,list_code_scanning_alerts.get_file_contents(repos, 2,230 avg tokens) is consistently the heaviest — prefer directory listings withfieldsfiltering over full-file fetches, and note the fixed ~550-token icon_metablock inflates every non-wrapper call (get_label,list_discussions,search_users,search_code) regardless of payload size. A wrapper that strips_meta.serverInfo.icons(following thelist_workflows/list_labelmcpscripts pattern) would meaningfully cut overhead across the board.Visualizations
Response Size by Toolset
Usefulness Ratings
Daily Token Trend
Size vs Usefulness
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