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 11 sources (10 GitHub MCP tools + the prompt-injected <github-context> block) across all available toolsets. Overall usefulness averaged 3.55/5, consuming ~17,586 tokens today (a single per-item call each).
Key findings
🥇 Best patterns:list_discussions and get_file_contents (both ⭐⭐⭐⭐⭐) — compact, cursor-paginated, relationship-rich, size proportional to payload.
⚠️Pagination defect:list_workflows ignored per_page=1 and returned all 329 workflows (~3,880 tokens) — the single largest avoidable context cost.
🚫 Identity tools blocked:get_teams returns 403 under the integration token (same as get_me) → agents must read identity from the <github-context> block, which is the most efficient source (⭐⭐⭐⭐⭐, ~0 MCP cost).
🔒 list_repository_collaborators blocked by integrity policy ("lower integrity than agent requires") — no user data reaches the agent (⭐⭐).
✅ list_code_scanning_alerts returned [] — no open critical/high alerts (healthy repo state).
Recommendations
Prefer for autonomous work: list_discussions, list_pull_requests, get_file_contents, and the injected <github-context> block.
Use with care (context-heavy):get_file_contents on large files (range-fetch), search_issues and list_issues (full bodies inflate cost — add a title-only mode for triage).
Avoid / substitute:get_teams + get_me (fall back to workflow context); list_workflows pagination cannot be trusted to bound output.
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.
-
MCP Structural Analysis — 2026-07-14
Analyzed 11 sources (10 GitHub MCP tools + the prompt-injected
<github-context>block) across all available toolsets. Overall usefulness averaged 3.55/5, consuming ~17,586 tokens today (a single per-item call each).Key findings
list_discussionsandget_file_contents(both ⭐⭐⭐⭐⭐) — compact, cursor-paginated, relationship-rich, size proportional to payload.list_workflowsignoredper_page=1and returned all 329 workflows (~3,880 tokens) — the single largest avoidable context cost.get_teamsreturns 403 under the integration token (same asget_me) → agents must read identity from the<github-context>block, which is the most efficient source (⭐⭐⭐⭐⭐, ~0 MCP cost).list_repository_collaboratorsblocked by integrity policy ("lower integrity than agent requires") — no user data reaches the agent (⭐⭐).list_code_scanning_alertsreturned[]— no open critical/high alerts (healthy repo state).Recommendations
list_discussions,list_pull_requests,get_file_contents, and the injected<github-context>block.get_file_contentson large files (range-fetch),search_issuesandlist_issues(full bodies inflate cost — add a title-only mode for triage).get_teams+get_me(fall back to workflow context);list_workflowspagination cannot be trusted to bound output.Full Structural Analysis Report
Executive Summary
list_discussions,get_file_contents,github_context— 5/5get_teams— 1/5 (403 under integration token)Usefulness Ratings for Agentic Work
Schema Analysis
[]no open alertsResponse Size Analysis
30-Day Trend Summary
Recommendations
list_discussions,get_file_contents,list_pull_requests,list_issues,search_issues, plus the injected<github-context>.list_workflows(honorper_page);get_teams/get_me(degrade gracefully or omit from read-only toolset);list_repository_collaborators(integrity-blocked).list_discussions(157 tok, 5/5),github_context(80 tok, 5/5),list_pull_requests(319 tok, 4/5).get_file_contentson large files (9.5k),list_workflows(3.9k, avoidable),search_issues(1.9k).Visualizations
Response Size by Toolset
Usefulness Ratings
Daily Token Trend
Size vs Usefulness
References: §29332024273
Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
awmgmcpgSee Network Configuration for more information.
Beta Was this translation helpful? Give feedback.
All reactions