MCP builder tools return wrong results without an error: `min`/`max` of a DateTime is 0, and unknown options such as `having` are silently ignored
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 55/100
- Issue 类型
- 缺陷
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- clickhouse, typescript
调研方向
Start with packages/common-utils/src/core/renderChartConfig.ts around lines 540–543 and packages/api/src/mcp/tools/query/table.ts around line 32; compare the generated aggregate SQL and how the input schema handles unknown keys. Reproduce both cases using the SQL example in the issue and a clickstack_table call with having. Done means DateTime min/max return timestamps and unsupported options produce a validation error or are applied as specified.
由索引模型根据 Issue 内容生成。
描述
Summary
Two cases where clickstack_table / clickstack_timeseries return a plausible-looking answer that is wrong, with no error or warning. Agents can't tell, so they build conclusions on them.
min/maxon a DateTime column return 0. Every non-count aggregate wraps its value intoFloat64OrDefault(toString(expr))(packages/common-utils/src/core/renderChartConfig.ts:540-543). ForDate/DateTime/DateTime64,toString()gives'2026-11-04 08:00:00.000000000', which doesn't parse as a float, so every value becomes 0 andmax(Timestamp)is 0.- Unknown options are dropped. The tool input schemas are plain
z.object(...)(e.g.tableSchemainpackages/api/src/mcp/tools/query/table.ts:32), so zod strips keys it doesn't know.having: "lines > 5"is accepted, the SQL has noHAVING, and rows with 1 come back. Agents tryhavingbecause dashboard tiles support it (packages/api/src/mcp/tools/dashboards/schemas.ts:839).
Environment
HyperDX 2-nightly image (late Oct 2026) with ClickHouse 26.10.3. Code references checked on main at d08b2fa7 (2026-11-03, 2.43.1).
Steps to reproduce
clickstack_tableon a log or trace source,select: [{aggFn: "min", valueExpression: "Timestamp", alias: "first_seen"}, {aggFn: "max", valueExpression: "Timestamp", alias: "last_seen"}], any time range with data.- Result:
first_seen: 0, last_seen: 0. The SQL insystem.query_logismax(toFloat64OrDefault(toString(Timestamp))).
The cast alone, on any ClickHouse:
WITH arrayJoin([toDateTime64('2026-11-04 07:59:01.123', 9), toDateTime64('2026-11-04 08:00:00', 9)]) AS Timestamp
SELECT max(toFloat64OrDefault(toString(Timestamp))) AS rendered, max(Timestamp) AS expected
-- rendered = 0, expected = 2026-11-04 08:00:00.000000000
clickstack_tablewithgroupByandhaving: "count > 5": no validation error, the generated SQL has noHAVING, and groups with count 1 are returned.
Expected vs actual
| Expected | Actual | |
|---|---|---|
max(Timestamp) |
the latest timestamp (or a clear error) | 0 |
unknown option having |
a validation error naming the valid options, or having applied |
silently ignored |
Impact
In 4 agent investigations on production-size data (about 170 MCP calls), 3 asked "first seen / last seen" questions and got 0 back, and 2 used having and got unfiltered results (one call returned 1,044 groups, which then hit response trimming, see #3542).
Proposed fix
min,maxandanydon't need a Float64 value. Pass the expression through uncast for them, or convert dates numerically (e.g.toUnixTimestamp64Milli) instead of viatoString. The aggregate already handles numbers and numeric strings today, so a type check (date-like → no cast) keeps that behaviour.- Make the MCP tool input schemas
.strict(), so an unknown key returns a validation error listing the accepted options. Addinghavingandlimittoclickstack_tableitself, as tiles already support, is part of #3542.
Related
- #3542: MCP response trimming, and
clickstack_tablehas nolimit,havingor default order - #3499:
valueExpressionignored on metric selects - #2311 / #3237:
count_distincton metric tiles
- 主要语言
- TypeScript
- 星标
- 10.1k
- 派生
- 527
- 平均合并
- 1 天 20 小时
- 30 天内合并 PR
- 186
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
ClickHouse/ClickStack 的其他 Issue
-
external
难度 2/5 1-3 小时 新手友好度 72/100
ClickHouse/ClickStack#3761 ·
维护者通常 1 天内回复
-
Metric chart with aggFn increase and a multi-column group-by fails: toString() gets several arguments可能已有人在做 @CG-5228 于 26 天前认领。 未关闭external
难度 2/5 1-3 小时 新手友好度 76/100
ClickHouse/ClickStack#3477 · 1 条评论 ·
维护者通常 1 天内回复
-
Slack notifications for inline alerts fail when the chart-explorer link passes Slack's 3000-character block limit可能已有人在做 @Tyagiquamar 于 27 天前认领。 未关闭alerting bug external
难度 2/5 1-3 小时 新手友好度 76/100
ClickHouse/ClickStack#3452 ·
维护者通常 1 天内回复
-
check-alerts worker: 13 error spans (mongodb.create, NamespaceExists) every minute because mongoose autoCreate is still on可能重新可做 关联的 PR 已关闭且未合并。 未关闭bug external Needs Feedback
难度 2/5 1-3 小时 新手友好度 72/100
ClickHouse/ClickStack#3308 · 1 条评论 ·
维护者通常 1 天内回复
-
count_distinct aggFn on metric tiles ignores valueExpression, always counts distinct metric Values可能已有人在做 @Harshul1484 于 54 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
ClickHouse/ClickStack#2311 ·
维护者通常 1 天内回复
查看 ClickHouse/ClickStack 的全部 Issue
相似的 Issue
-
Add: GTrekker未关闭check:passed streams:add
难度 1/5 1 小时以内 新手友好度 72/100
维护者通常 1 天内回复
-
area: ui Bug Payload OSS
难度 1/5 1 小时以内 新手友好度 88/100
payloadcms/payload#19839 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 85/100
维护者通常 1 天内回复
-
fix(auth): add the email OTP verification step to Pollar login可能已有人在做 @akansnoro 今天认领。 未关闭Stellar Wave
难度 2/5 1-3 小时 新手友好度 74/100
safetrustcr/dApp-SafeTrust#584 · 10 条评论 ·
维护者通常 1 天内回复
-
The manager preset saves launch definitions without the required file and digest pair可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭bug
难度 2/5 1-3 小时 新手友好度 80/100
维护者通常 1 天内回复