[mcp-analysis] MCP Structural Analysis - 2026-03-24

[github-actions[bot]]

Analyzed 9 tools across 8 toolsets today. Average usefulness rating: 3.44/5. Top performers: list_discussions, get_label, search_repositories (all 5/5). Critical failure: list_code_scanning_alerts (137KB response, no pagination — context limit exceeded). Rating trend over 30 days: stable (~3.0 avg).

Full Structural Analysis Report

Executive Summary

Metric	Value
Tools Analyzed	9
Total Tokens (Today)	42,569
Average Usefulness Rating	3.44 / 5
Best Rated Tools	list_discussions, get_label, search_repositories: 5/5
Worst Rated Tools	get_me (403 error), list_code_scanning_alerts (context overflow): 1/5
30-Day Data Points	219
Avg Daily Tokens	~31,025
Rating Trend	Stable (early: 3.08, recent: 3.03)

---

Usefulness Ratings for Agentic Work

Tool	Toolset	Rating	Assessment
list_discussions	discussions	⭐⭐⭐⭐⭐	Compact, paginated, cursor-based — excellent for agents
get_label	labels	⭐⭐⭐⭐⭐	Minimal flat object (~25 tokens), all needed fields
search_repositories	search	⭐⭐⭐⭐⭐	Rich metadata, minimal_output=true prevents bloat
get_file_contents	repos	⭐⭐⭐⭐	Full content returned; large files inflate context
list_issues	issues	⭐⭐⭐⭐	Complete data; issue bodies can be very large
list_pull_requests	pull_requests	⭐⭐⭐⭐	Good PR metadata; minor avatar_url bloat in user obj
list_workflows	actions	⭐⭐	per_page param ignored — returns 30 even when 1 requested; triple URL fields (url/html_url/badge_url) are redundant
get_me	context	⭐	403 Not accessible — unavailable in this integration
list_code_scanning_alerts	code_security	⭐	137,614 chars — exceeds context limit; no per_page; deeply nested (depth 5); unusable without pagination fix

---

Schema Analysis

Tool	Type	Depth	Key Fields	Notes
get_me	error	0	—	403 integration error
get_file_contents	object	2	sha, text, mimeType, uri	Content in resource block
list_issues	array	3	number, title, state, body, labels, user	Labels embedded
list_pull_requests	array	4	number, title, state, body, head, base, user	head/base nest repo info
list_workflows	object	3	id, name, path, state, url, html_url, badge_url	Triple URL redundancy
list_code_scanning_alerts	array	5	number, rule.id, severity, location.path	Deeply nested, no page limit
list_discussions	object	3	number, title, category.name, pageInfo, totalCount	Cursor pagination ✅
get_label	object	1	id, name, color, description	Flat, minimal ✅
search_repositories	array	2	full_name, language, topics, stars, forks	Clean summary data ✅

---

Response Size Analysis

Toolset	Tokens (Today)	Notes
code_security	34,400	Context overflow — no per_page support
actions	4,200	per_page param ignored
repos	1,900	Scales with file size
issues	1,350	Scales with body length
pull_requests	480	Reasonable for 1 PR
search	125	Efficient with minimal_output
discussions	75	Most context-efficient paginated list
labels	25	Smallest response, most focused
context	14	Error response only

---

Visualizations

Response Size by Toolset

Usefulness Ratings

30-Day Token Trend

Size vs Usefulness (Ideal: top-left)

---

Recommendations

High-value tools (rating 4–5, use freely):

• list_discussions, get_label, search_repositories — minimal tokens, complete data
• list_issues, list_pull_requests, get_file_contents — good data; apply perPage=1 to control size

Tools needing improvement:

• list_workflows — must honor per_page parameter; triple URL fields (url/html_url/badge_url) should be consolidated
• list_code_scanning_alerts — critically needs per_page pagination; current response is unusable for agents

Context-efficient picks (low tokens + high rating):

• get_label (25 tokens, ⭐⭐⭐⭐⭐), list_discussions (75 tokens, ⭐⭐⭐⭐⭐), search_repositories (125 tokens, ⭐⭐⭐⭐⭐)

Context-heavy tools to handle carefully:

• list_code_scanning_alerts — avoid without per_page fix; proxy via file read
• list_workflows — request only the fields needed; current response is ~4× larger than necessary

References:

• §23486670077

AI generated by GitHub MCP Structural Analysis · history

• expires on Mar 25, 2026, 11:21 AM UTC

[github-actions[bot]]

This discussion has been marked as outdated by GitHub MCP Structural Analysis.

A newer discussion is available at Discussion #22870.