| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Updates MCP tool annotation titles so MCP client UIs better reflect that some “issue” tools also apply to pull requests (since PRs are issues in GitHub’s API), and propagates those metadata changes into generated docs/snapshots.
Changes:
| File | Description |
|---|---|
| README.md | Updates generated tool listing strings for the new annotation titles. |
| pkg/github/issues.go | Changes annotations.title for add_issue_comment and issue_write. |
| pkg/github/toolsnaps/add_issue_comment.snap | Updates snapshot to reflect add_issue_comment title change. |
| pkg/github/toolsnaps/issue_write.snap | Updates snapshot to reflect issue_write title change. |
Sorry, something went wrong.
| Description: t("TOOL_ISSUE_WRITE_DESCRIPTION", "Create a new or update an existing issue in a GitHub repository."), | ||
| Annotations: &mcp.ToolAnnotations{ | ||
| Title: t("TOOL_ISSUE_WRITE_USER_TITLE", "Create or update issue."), | ||
| Title: t("TOOL_ISSUE_WRITE_USER_TITLE", "Create or update issue/pull request"), |
There was a problem hiding this comment.
This is true - but it seems like it would be too confusing to add this context to the title.
Sorry, something went wrong.
…tool-mapping # Conflicts: # README.md # pkg/github/__toolsnaps__/issue_write.snap # pkg/github/issues.go
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
I don't love the leaky abstraction, but this is technically accurate and users are fine to know this. Models should not be getting these fields. |
Sorry, something went wrong.
There was a problem hiding this comment.
Security ip
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Summary
This updates our tool title annotations for tools that can operate on issues AND pull requests to clarify that they work with issues and pull requests: issue_write and add_issue_comment.
The current titles only mention issues, which can be confusing in MCP clients when the tools are being used.
Why
When these tools appear in client UIs, issue-only wording is confusing and can mislead users/agents into thinking PR operations are unsupported.
What changed
MCP impact
This change updates tool metadata (annotations.title) exposed to MCP clients so tool labeling in UI better matches actual capability. Runtime behavior is unchanged.
Prompts tested (tool changes only)
Security / limits
Tool renaming
Lint & tests
Docs