Testing the feedback tool sends real feedback
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 35/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- typescript
调研方向
Start with the tool definition in packages/mcp-core/src/tools/catalog/submit-feedback-to-sentry-team.ts, especially the hints around line 73 and the input schema around lines 78-109. Then check packages/mcp-core/src/server.ts near line 405, where the outputSchema is published, and availability.ts lines 123-127, which hide the tool without a DSN. Done means a dry-run input that validates and returns the same response shape without capturing feedback, with the design for the DSN-less case settled first.
由索引模型根据 Issue 内容生成。
描述
submit_feedback_to_sentry_team has no way to be exercised without capturing a real User Feedback in mcp-server. Its hints say not to call it for testing (packages/mcp-core/src/tools/catalog/submit-feedback-to-sentry-team.ts:73), but clients that verify the tool or record tool response shapes call it anyway, and every call lands in the feedback inbox.
- MCP-SERVER-GQ6 (2026-11-14 05:15 UTC): an
other-family client (python-httpx) asked for a dry-run flag because "building a faithful client or replica means sending real feedback." - The same caller (matched by client IP; no
mcp.session.idoruser.idwas recorded) called ~100 tools between 05:10 and 05:15 UTC while documenting response shapes, including writes likecreate_team,create_projectandupdate_dsn. It calledsubmit_feedback_to_sentry_teamthree times in five seconds: one probe rejected for an oversizedtoolName, then MCP-SERVER-GQ7 (asks to document the result text) and MCP-SERVER-GQ6. Both returned{"feedbackId": ...}. - Other test or meta submissions in the last 30 days: MCP-SERVER-GH9 and MCP-SERVER-GHA (2026-10-30, a maintainer checking end-to-end delivery through the hosted connector), MCP-SERVER-GP8 (2026-11-12, feedback about the feedback tool).
- The tool has no
dryRuninput (submit-feedback-to-sentry-team.ts:78-109), and no MCP tool in mcp-core has one. Its result shape is already published asoutputSchemaintools/list(packages/mcp-core/src/server.ts:405). Locally it can't be used as a sandbox either: it's hidden when Sentry telemetry has no DSN (packages/mcp-core/src/tools/catalog-runtime/availability.ts:123-127).
Proposal from the reporter of MCP-SERVER-GQ6: add a dry-run flag that validates input and returns the response shape without capturing feedback.
via Sentry.
--
- 主要语言
- TypeScript
- 星标
- 961
- 派生
- 179
- 平均合并
- 15 小时 33 分钟
- 30 天内合并 PR
- 476
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
getsentry/toolkit 的其他 Issue
-
MCP mcp-feedback-pattern
难度 2/5 1-3 小时 新手友好度 78/100
getsentry/toolkit#2276 · 1 条评论 ·
维护者通常 1 天内回复
-
CLI enhancement MCP
难度 2/5 1-3 小时 新手友好度 63/100
getsentry/toolkit#1908 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
getsentry/toolkit#1471 · 1 条评论 ·
维护者通常 1 天内回复
-
get_sentry_resource gives no guidance for Explore > Errors list URLs可能已有人在做 @sentry-junior 今天认领。 未关闭MCP mcp-feedback-pattern
难度 2/5 1-3 小时 新手友好度 32/100
getsentry/toolkit#2278 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 3/5 1-2 天 新手友好度 65/100
getsentry/toolkit#2275 · 1 条评论 ·
维护者通常 1 天内回复
查看 getsentry/toolkit 的全部 Issue
相似的 Issue
-
Add: BOM Cine未关闭approved check:passed streams:add
难度 1/5 1 小时以内 新手友好度 72/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
bug platform-android
难度 2/5 1-3 小时 新手友好度 68/100
Termix-SSH/Mobile#146 · 1 条评论 ·
维护者通常 2 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 66/100
devswha/herdr-web-ui#3875 ·
-
难度 1/5 1 小时以内 新手友好度 88/100