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
Generated: 2026-05-24 MCP Mode: Remote (read-only session) Toolsets: All Previous Report: None (first run — no cache found at /tmp/gh-aw/cache-memory/github-mcp-tools.json)
Note on read-only visibility: The tools enumerated below are those exposed to a read-only MCP session (X-MCP-Readonly: true). The JSON mapping in this repo contains the full toolset, including write operations (e.g. issue_write, create_pull_request, label_write, merge_pull_request, star_repository). This report documents both: visible read tools are listed in tables, and write-only tools registered in the JSON mapping are surfaced in the "Write Tools (not visible in this session)" callouts.
Inconsistency Detection
Toolset Integrity Checks
✅ No duplicate tool names across toolsets in the JSON mapping.
✅ Naming patterns are consistent: read operations use get_*/list_*/search_* prefixes; write operations use *_write/create_*/update_*/merge_* patterns or aggregated *_write resource tools (e.g. issue_write, label_write).
⚠️Empty toolset detected: The users toolset has zero registered tools — search_users actually lives in the search toolset. This is intentional but worth flagging.
⚠️Naming asymmetry: list_label (singular) vs. list_labels would be more consistent with list_issues, list_commits, etc. This name comes from the upstream MCP server, so it cannot be changed locally; flagged here for awareness.
⚠️Stale users entry in github_tool_to_toolset.json: that file references get_user / list_users under users, but neither tool exists in the current MCP server. The authoritative mapping is github_toolsets_permissions.json. Recommend a follow-up to reconcile or deprecate github_tool_to_toolset.json.
JSON Mapping Comparison
Discrepancies Between MCP Server and JSON Mapping
Summary:
Total Discrepancies: 1
Missing Tools (in JSON but not in MCP): 0
Extra Tools (in MCP but not in JSON): 1
Moved Tools (different toolset): 0
Extra Tools (in MCP but not in JSON)
Toolset
Tool Name
Action Taken
repos
list_repository_collaborators
✅ Added to repos toolset in JSON mapping
Why this matters: list_repository_collaborators is already referenced by the workflow at .github/workflows/daily-doc-healer.md:98 (where the agent inspects collaborators to classify PR closure intent). Without an entry in the toolsets/permissions mapping, the compiler cannot route the tool to its contents read permission.
Action: Opened PR with branch update-github-mcp-tools-mapping adding the tool to the repos toolset and updating documentation.
Changes Since Last Report
No previous cache file existed, so no diff is computable for this run. A baseline cache has been written to /tmp/gh-aw/cache-memory/github-mcp-tools.json and will enable diff reporting on the next run.
Not visible in this read-only session, but registered in the JSON mapping: enable_toolset, get_toolset_tools, list_available_toolsets
Recommended Default Toolsets
Recommended Defaults (current and confirmed): context, repos, issues, pull_requests
Rationale:
context — get_me/get_teams provide identity awareness needed by almost every workflow.
repos — File reads, commits, branches, releases, tags, collaborators (newly added). Foundational for any code-aware agent.
issues — Issue triage, listing, and search are central to CI/CD automation.
pull_requests — Code review, diff inspection, and merge automation depend on this toolset.
Note: The currently-documented defaults exclude users because that toolset is empty (user search is provided by search.search_users). No changes are recommended here.
Read-only session limits visibility: Only 55 tools were visible to this enumeration run because X-MCP-Readonly: true filters out write operations. The full MCP server exposes ~90 tools across all toolsets.
Single discrepancy found and fixed: list_repository_collaborators was the only tool present in the MCP server but missing from the JSON mapping. PR opened to fix.
Aggregated resource tools: The MCP server uses aggregated tools like pull_request_read (with method parameter for sub-operations: get, get_diff, get_files, get_reviews, etc.), actions_get/actions_list, issue_read, projects_get/projects_list. Workflow authors should reference the method parameter for fine-grained operations.
users toolset is intentionally empty: User-related queries live in search_users under the search toolset.
Documentation is now in sync with the corrected JSON mapping.
Methodology
Discovery: Self-inspection of mcp__github__* tools exposed in this read-only MCP session.
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.
-
Generated: 2026-05-24
MCP Mode: Remote (read-only session)
Toolsets: All
Previous Report: None (first run — no cache found at
/tmp/gh-aw/cache-memory/github-mcp-tools.json)Executive Summary
Inconsistency Detection
Toolset Integrity Checks
get_*/list_*/search_*prefixes; write operations use*_write/create_*/update_*/merge_*patterns or aggregated*_writeresource tools (e.g.issue_write,label_write).userstoolset has zero registered tools —search_usersactually lives in thesearchtoolset. This is intentional but worth flagging.list_label(singular) vs.list_labelswould be more consistent withlist_issues,list_commits, etc. This name comes from the upstream MCP server, so it cannot be changed locally; flagged here for awareness.usersentry ingithub_tool_to_toolset.json: that file referencesget_user/list_usersunderusers, but neither tool exists in the current MCP server. The authoritative mapping isgithub_toolsets_permissions.json. Recommend a follow-up to reconcile or deprecategithub_tool_to_toolset.json.JSON Mapping Comparison
Discrepancies Between MCP Server and JSON Mapping
Summary:
Extra Tools (in MCP but not in JSON)
reposlist_repository_collaboratorsrepostoolset in JSON mappingWhy this matters:
list_repository_collaboratorsis already referenced by the workflow at.github/workflows/daily-doc-healer.md:98(where the agent inspects collaborators to classify PR closure intent). Without an entry in the toolsets/permissions mapping, the compiler cannot route the tool to itscontentsread permission.Action: Opened PR with branch
update-github-mcp-tools-mappingadding the tool to therepostoolset and updating documentation.Changes Since Last Report
No previous cache file existed, so no diff is computable for this run. A baseline cache has been written to
/tmp/gh-aw/cache-memory/github-mcp-tools.jsonand will enable diff reporting on the next run.Tools by Toolset
context
Description: GitHub Actions context and environment (identity, teams).
Source: pkg/github/context_tools.go
repos
Description: Repository operations.
Source: pkg/github/repositories.go
get_commitowner,repo,sha,include_diffget_file_contentsowner,repo,path,refget_latest_releaseowner,repoget_release_by_tagowner,repo,tagget_tagowner,repo,taglist_branchesowner,repo,page,perPagelist_commitsowner,repo,sha,path,author,since,untillist_releasesowner,repo,page,perPagelist_repository_collaborators✨owner,repo,affiliation,page,perPagelist_tagsowner,repo,page,perPagegit
Description: Git API operations (tree, refs).
Source: pkg/github/repositories.go
get_repository_treeowner,repo,tree_sha,recursive,path_filterissues
Description: Issue management.
Source: pkg/github/issues.go
issue_readowner,repo,issue_number,methodlist_issue_typesownerlist_issuesowner,repo,state,labels,orderBysearch_issuesquery,owner,repo,sortpull_requests
Description: Pull request operations.
Source: pkg/github/pullrequests.go
list_pull_requestsowner,repo,state,head,base,sortpull_request_readowner,repo,pullNumber,methodsearch_pull_requestsquery,owner,repo,sortactions
Description: GitHub Actions workflows.
Source: pkg/github/actions.go
actions_getowner,repo,method,resource_idactions_listowner,repo,method,resource_idget_job_logsowner,repo,job_idorrun_id+failed_onlycode_security
Description: Code scanning alerts.
Source: pkg/github/code_scanning.go
get_code_scanning_alertowner,repo,alertNumberlist_code_scanning_alertsowner,repo,state,severity,tool_namedependabot
Description: Dependabot alerts.
Source: pkg/github/dependabot.go
get_dependabot_alertowner,repo,alertNumberlist_dependabot_alertsowner,repo,state,severitydiscussions
Description: GitHub Discussions.
Source: pkg/github/discussions.go
get_discussionowner,repo,discussionNumberget_discussion_commentsowner,repo,discussionNumber,includeReplieslist_discussion_categoriesowner,repolist_discussionsowner,repo,category,orderBy,directiongists
Description: Gist operations.
Source: pkg/github/gists.go
get_gistgist_idlist_gistsusername,since,pagelabels
Description: Label management.
Source: pkg/github/labels.go
get_labelowner,repo,namelist_labelowner,reponotifications
Description: Notification management.
Source: pkg/github/notifications.go
get_notification_detailsnotificationIDlist_notificationsfilter,since,before,owner,repoorgs
Description: Organization operations.
Source: pkg/github/security_advisories.go (for
list_org_repository_security_advisories)list_org_repository_security_advisoriesorg,state,sort,directionprojects
Description: GitHub Projects (requires PAT —
GITHUB_TOKENlacksprojectscope).Source: pkg/github/projects.go
projects_getmethod,owner,project_number,item_id,field_idprojects_listmethod,owner,project_number,querysearch
Description: Advanced search across GitHub (keyword + semantic).
Source: pkg/github/search.go
search_codequery,sort,ordersearch_orgsquery,sort,ordersearch_repositoriesquery,sort,order,minimal_outputsearch_usersquery,sort,ordersemantic_issue_similarity_searchowner,repo,issue_number,thresholdsemantic_issues_searchquery,owner,repo,sortsecret_protection
Description: Secret scanning.
Source: pkg/github/secret_scanning.go
get_secret_scanning_alertowner,repo,alertNumberlist_secret_scanning_alertsowner,repo,state,resolution,secret_typerun_secret_scanningfiles,owner,reposecurity_advisories
Description: Security advisories.
Source: pkg/github/security_advisories.go
check_dependency_vulnerabilitiesowner,repo,dependenciesget_global_security_advisoryghsaIdlist_global_security_advisoriestype,severity,ecosystem,cveIdlist_repository_security_advisoriesowner,repo,state,sortstargazers
Description: Repository stars.
Source: pkg/github/repositories.go
list_starred_repositoriesusername,sort,directionusers
Description: User information.
Source: pkg/github/search.go (for
search_users)copilot_spaces (remote-only)
Description: GitHub Copilot Spaces — only available in remote MCP mode.
Source: github-mcp-server remote endpoints (not in local
pkg/github/)get_copilot_spaceowner,namelist_copilot_spacesgithub_support_docs_search (remote-only)
Description: GitHub support documentation search — remote MCP mode only.
github_support_docs_searchqueryexperiments
Description: Experimental — dynamic toolset management.
Source: pkg/github/dynamic_tools.go
Recommended Default Toolsets
Recommended Defaults (current and confirmed):
context,repos,issues,pull_requestsRationale:
context—get_me/get_teamsprovide identity awareness needed by almost every workflow.repos— File reads, commits, branches, releases, tags, collaborators (newly added). Foundational for any code-aware agent.issues— Issue triage, listing, and search are central to CI/CD automation.pull_requests— Code review, diff inspection, and merge automation depend on this toolset.Note: The currently-documented defaults exclude
usersbecause that toolset is empty (user search is provided bysearch.search_users). No changes are recommended here.Specialized Toolsets (enable explicitly):
actions— workflow introspection / triggeringcode_security,dependabot,secret_protection,security_advisories— security workflowsdiscussions— community/Q&A workflowsgists,labels,notifications,orgs,stargazers— narrow automation needsprojects— requires PAT (notGITHUB_TOKEN)search— cross-repo discoverycopilot_spaces,github_support_docs_search— remote-mode onlyexperiments— toolset-management meta toolsToolset Configuration Reference
Full list of toolset names
actions,code_security,context,copilot_spaces,dependabot,discussions,experiments,gists,git,github_support_docs_search,issues,labels,notifications,orgs,projects,pull_requests,repos,search,secret_protection,security_advisories,stargazers,usersNotes and Observations
X-MCP-Readonly: truefilters out write operations. The full MCP server exposes ~90 tools across all toolsets.list_repository_collaboratorswas the only tool present in the MCP server but missing from the JSON mapping. PR opened to fix.pull_request_read(withmethodparameter for sub-operations:get,get_diff,get_files,get_reviews, etc.),actions_get/actions_list,issue_read,projects_get/projects_list. Workflow authors should reference themethodparameter for fine-grained operations.userstoolset is intentionally empty: User-related queries live insearch_usersunder thesearchtoolset.Methodology
mcp__github__*tools exposed in this read-only MCP session.pkg/github/source files./tmp/gh-aw/cache-memory/github-mcp-tools.jsonto enable diff reporting on subsequent runs.References:
Beta Was this translation helpful? Give feedback.
All reactions