You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Analyzed 10 representative GitHub MCP tools across all available toolsets on 2026-09-30. Average usefulness held steady at 3.0/5; the standout finding is that get_file_contents swung from rating 4 (small file) to rating 1 (README.md, ~12.6K tokens, no truncation/pagination support) purely based on which file was requested — a reminder that response quality for this tool is caller-controlled, not tool-controlled. search_code again failed to GitHub API rate limiting (429), continuing a recurring reliability gap. The persistent integrity-policy filtering on list_issues (21/21 days) continues to silently hide the one open issue in every measured run.
Metric
Value
Tools Analyzed
10
Total Tokens (Today)
18,765
Average Usefulness Rating
3.0/5
Best Rated Tool
github_context: 5/5
Worst Rated Tool
search_code: 1/5 (tied with get_file_contents: 1/5)
Full Structural Analysis Report
Usefulness Ratings for Agentic Work
Tool
Toolset
Rating
Assessment
github_context
workflow_context
⭐⭐⭐⭐⭐
Excellent — zero-cost injected identity block
list_workflows (mcpscripts wrapper)
actions
⭐⭐⭐⭐⭐
Excellent — clean JSON, explicit pagination, no bloat
list_pull_requests
pull_requests
⭐⭐⭐⭐
Good — flat, minimal, directly actionable
get_label
labels
⭐⭐⭐
Adequate — tiny payload but icon _meta overhead dominates
list_code_scanning_alerts
code_security
⭐⭐⭐
Adequate — useful but repeated rule.help boilerplate bloats payload
list_discussions
discussions
⭐⭐⭐
Adequate — good pagination metadata, icon overhead persists
search_users
users
⭐⭐⭐
Adequate — minimal identity fields only
list_issues
issues
⭐⭐
Limited — integrity-filtered issue makes array falsely appear empty
search_code
search
⭐
Poor — failed with 429 rate limit, zero usable data
get_file_contents
repos
⭐
Poor (this run) — README.md returned as a single 50K-char line, spilled to a side file near the 25K-token ceiling
README.md near 25K-token ceiling, no truncation support
30-Day Trend Summary
Metric
Value
Data Points
180
Average Daily Tokens
14,281
Average Rating Trend
Stable — code_security and repos remain the two heaviest toolsets by a wide margin; list_workflows and list_pull_requests remain consistently lean and high-rated
Recommendations
High-value tools (rating 4-5): github_context (free), list_workflows via mcpscripts wrapper, list_pull_requests with fields filtering — prefer these patterns whenever available.
Tools needing improvement: list_issues (integrity-filtered results silently look like "no issues" — agents should check for filtered-item warnings before concluding an empty result set is real); search_code (rate-limit fragility warrants retry/backoff logic); list_code_scanning_alerts (server-side dedup of repeated rule.help text across same-rule alerts would meaningfully cut payload size).
Context-efficient tools (low tokens, high rating): github_context, list_workflows, list_pull_requests — all under 200 tokens with ratings ≥4.
Context-heavy tools (high tokens): code_security (7,761 avg) and repos (3,357 avg, but caller-dependent — a targeted small file like CODEOWNERS runs ~700 tokens vs. README.md's 12,600+). Always check file size via a directory listing before calling get_file_contents on an unknown file.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Analyzed 10 representative GitHub MCP tools across all available toolsets on 2026-09-30. Average usefulness held steady at 3.0/5; the standout finding is that
get_file_contentsswung from rating 4 (small file) to rating 1 (README.md, ~12.6K tokens, no truncation/pagination support) purely based on which file was requested — a reminder that response quality for this tool is caller-controlled, not tool-controlled.search_codeagain failed to GitHub API rate limiting (429), continuing a recurring reliability gap. The persistent integrity-policy filtering onlist_issues(21/21 days) continues to silently hide the one open issue in every measured run.github_context: 5/5search_code: 1/5 (tied withget_file_contents: 1/5)Full Structural Analysis Report
Usefulness Ratings for Agentic Work
github_contextlist_workflows(mcpscripts wrapper)list_pull_requestsget_label_metaoverhead dominateslist_code_scanning_alertsrule.helpboilerplate bloats payloadlist_discussionssearch_userslist_issuessearch_codeget_file_contentsSchema Analysis
github_contextlist_workflowslist_pull_requestsget_labellist_code_scanning_alertslist_discussionssearch_userslist_issuessearch_codeget_file_contentsResponse Size Analysis (30-day average)
Tool-by-Tool Analysis (Today)
github_contextlist_workflowslist_pull_requestsget_labelbuglabel, 4 real fields under icon overheadlist_code_scanning_alertslist_discussionssearch_userslist_issuessearch_codeget_file_contents30-Day Trend Summary
list_workflowsandlist_pull_requestsremain consistently lean and high-ratedRecommendations
github_context(free),list_workflowsvia mcpscripts wrapper,list_pull_requestswithfieldsfiltering — prefer these patterns whenever available.list_issues(integrity-filtered results silently look like "no issues" — agents should check for filtered-item warnings before concluding an empty result set is real);search_code(rate-limit fragility warrants retry/backoff logic);list_code_scanning_alerts(server-side dedup of repeatedrule.helptext across same-rule alerts would meaningfully cut payload size).github_context,list_workflows,list_pull_requests— all under 200 tokens with ratings ≥4.code_security(7,761 avg) andrepos(3,357 avg, but caller-dependent — a targeted small file like CODEOWNERS runs ~700 tokens vs. README.md's 12,600+). Always check file size via a directory listing before callingget_file_contentson an unknown file.Visualizations
Response Size by Toolset
Usefulness Ratings
Daily Token Trend
Size vs Usefulness
All reactions