Summary

This PR consolidates multiple repository tools in the repos toolset into unified tools with amethod parameter. This aims to reduce tool count/context size bloat by using the github mcp server.

Consolidations

1.file_write (3 → 1 tool)

Consolidates file write operations:

• create_or_update_file →file_write withmethod: "create" ormethod: "update"
• push_files →file_write withmethod: "push_files"
• delete_file →file_write withmethod: "delete"

Logic: All three tools perform file modifications in a repository and share the same required parameters (owner,repo,branch,message).

2.release_read (5 → 1 tool)

Consolidates release and tag read operations:

• list_tags →release_read withmethod: "list_tags"
• get_tag →release_read withmethod: "get_tag"
• list_releases →release_read withmethod: "list_releases"
• get_latest_release →release_read withmethod: "get_latest_release"
• get_release_by_tag →release_read withmethod: "get_release_by_tag"

Logic: These tools all read release/tag information from a repository and share the same required parameters (owner,repo).

3.commit_read (2 → 1 tool)

Consolidates commit read operations:

• get_commit →commit_read withmethod: "get"
• list_commits →commit_read withmethod: "list"

Logic: Both tools read commit data from a repository and share the same required parameters (owner,repo).

Not Consolidated

The following tools were kept separate as they operate on different entities or lack shared parameters:

• search_repositories,search_code - Search tools with distinct use cases
• get_file_contents - Requires special raw client handling
• list_branches - No natural pairing with other tools
• create_repository,fork_repository,create_branch - Different entities (repos vs branches), minimal parameter overlap

Results

• Tool count reduction: 17 tools → 10 tools (41% reduction in repos read/write tools)