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
11 GitHub MCP tools analyzed across 3 days (Feb 22–24, 2026). Today's total context footprint: 23,926 tokens across 11 tools. Average usefulness rating: 3.09/5. Two tools remain inaccessible (403), while list_discussions and search_repositories lead with perfect 5/5 ratings. list_code_scanning_alerts continues to dominate token consumption at 13,514 tokens per call.
Quick Summary
Metric
Value
Tools Analyzed
11
Total Tokens (Today)
23,926
Average Usefulness Rating
3.09/5
Best Rated
list_discussions, search_repositories — 5/5
Worst Rated
get_me, list_notifications — 1/5 (403 errors)
Most Token-Heavy
list_code_scanning_alerts — 13,514 tokens
Most Token-Efficient
get_label — 25 tokens
Full Structural Analysis Report
Usefulness Ratings for Agentic Work
Tool
Toolset
Rating
Assessment
list_discussions
discussions
⭐⭐⭐⭐⭐
Excellent — compact, paginated, all key fields immediately actionable
search_repositories
search
⭐⭐⭐⭐⭐
Excellent — rich metadata (topics, stars, language) in one call
list_commits
repos
⭐⭐⭐⭐
Good — clean nested structure, author + committer data, actionable
list_issues
issues
⭐⭐⭐⭐
Good — full issue data with pagination; body size is variable
get_label
labels
⭐⭐⭐⭐
Good — flat object, minimal tokens, all needed fields present
list_pull_requests
pull_requests
⭐⭐⭐
Adequate — payload offloaded to file; extra read step required
list_workflows
actions
⭐⭐⭐
Adequate — payload offloaded; ignores per_page=1 (returns all 205)
* get_label (single item). ** Feb 22 included list_label (2,755 tokens) which inflates this average.
Tool-by-Tool Analysis — Feb 24, 2026
Tool
Toolset
Tokens
Schema
Depth
Rating
Notes
get_me
context
13
error
0
1/5
403 - not accessible by integration
get_file_contents
repos
14
string
1
2/5
Returns SHA only; no file content inline
list_commits
repos
225
array
3
4/5
Clean, compact, actionable
list_issues
issues
1,400
object
3
4/5
Good; body length varies by issue
list_pull_requests
pull_requests
4,542
array
4
3/5
Payload file (18,169 chars original)
list_workflows
actions
3,940
object
3
3/5
Payload file (15,748 chars); ignores per_page
list_code_scanning_alerts
code_security
13,514
array
5
2/5
Payload file (54,058 chars); no per-page
list_discussions
discussions
105
object
3
5/5
Excellent — perfectly sized
get_label
labels
25
object
1
4/5
Ideal flat object
search_repositories
search
135
object
3
5/5
Rich, compact, immediately useful
list_notifications
notifications
13
error
0
1/5
403 - not accessible by integration
3-Day Trend Summary
Date
Tools
Total Tokens
Avg Rating
Feb 22
12
39,817
3.08/5
Feb 23
11
23,811
3.00/5
Feb 24
11
23,926
3.09/5
The Feb 22 spike was driven by list_code_scanning_alerts returning 25,476 tokens (vs ~13,514 on subsequent days, reflecting fewer open alerts in the payload), plus the inclusion of list_label (2,755 tokens). Token usage has stabilized around ~24k/day for the current 11-tool test set.
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.
-
11 GitHub MCP tools analyzed across 3 days (Feb 22–24, 2026). Today's total context footprint: 23,926 tokens across 11 tools. Average usefulness rating: 3.09/5. Two tools remain inaccessible (403), while
list_discussionsandsearch_repositorieslead with perfect 5/5 ratings.list_code_scanning_alertscontinues to dominate token consumption at 13,514 tokens per call.Quick Summary
list_discussions,search_repositories— 5/5get_me,list_notifications— 1/5 (403 errors)list_code_scanning_alerts— 13,514 tokensget_label— 25 tokensFull Structural Analysis Report
Usefulness Ratings for Agentic Work
list_discussionssearch_repositorieslist_commitslist_issuesget_labellist_pull_requestslist_workflowsper_page=1(returns all 205)list_code_scanning_alertsget_file_contentsget_melist_notificationsSchema Analysis
get_meget_file_contentslist_commitslist_issueslist_pull_requestslist_workflowslist_code_scanning_alertslist_discussionsget_labelsearch_repositorieslist_notificationsResponse Size Analysis
list_code_scanning_alertslist_pull_requestslist_workflowslist_issuesget_label(+list_labelFeb 22)search_repositoriesget_file_contents,list_commitslist_discussionsget_melist_notifications*
get_label(single item). ** Feb 22 includedlist_label(2,755 tokens) which inflates this average.Tool-by-Tool Analysis — Feb 24, 2026
get_meget_file_contentslist_commitslist_issueslist_pull_requestslist_workflowslist_code_scanning_alertslist_discussionsget_labelsearch_repositorieslist_notifications3-Day Trend Summary
The Feb 22 spike was driven by
list_code_scanning_alertsreturning 25,476 tokens (vs ~13,514 on subsequent days, reflecting fewer open alerts in the payload), plus the inclusion oflist_label(2,755 tokens). Token usage has stabilized around ~24k/day for the current 11-tool test set.Recommendations
High-value tools (rating 4–5, use freely):
list_discussions(105 tokens),search_repositories(135 tokens),list_commits(225 tokens),get_label(25 tokens),list_issues(variable, ~600–1400 tokens)Context-efficient sweet spot (low tokens + high rating):
get_label→ 25 tokens / 4⭐list_discussions→ 105 tokens / 5⭐search_repositories→ 135 tokens / 5⭐list_commits→ 225 tokens / 4⭐Tools needing improvement:
list_code_scanning_alerts— Needs per-page filtering; currently returns entire alert set regardless of paramslist_workflows/list_pull_requests—per_pageparameter ignored or not enforced; payload redirect adds frictionget_file_contents— Should return file content directly rather than saving to disk silentlyUnavailable in this environment (403):
get_me,list_notifications— Integration token does not have user-level scopesVisualizations
Response Size by Toolset (3-Day Comparison)
Usefulness Ratings by Toolset
Daily Token Usage Trend
Token Size vs Usefulness (Scatter)
References: §22348447807
Beta Was this translation helpful? Give feedback.
All reactions