feat: expose MCP tool annotations for tool grouping#23195
Conversation
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 617fcc888f
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
ThomasK33
left a comment
There was a problem hiding this comment.
LGTM. I think Codex has a point about that annotation potentially being read-only for port forwards, but I'll leave it up to you.
|
Addressed the port-forward annotation feedback in 67083c0. The workspace port-forward tool now uses read-only/idempotent MCP hints, and I added a regression test covering that classification. |
Summary
Why
readOnlyHint,destructiveHint,idempotentHint,openWorldHint).toolsdkand has both MCP servers emit those hints throughmcp.Tool.Annotations, avoiding drift between local and remote MCP implementations.Testing
Note: Done using Coder Agents, reviewed and tested by human locally