You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(hyperdx): tolerate JSON-encoded array/number params from MCP transport (#432)
Some MCP transport bridges JSON-stringify structured params (arrays, objects)
and numeric params before delivering them to the server. Real session reports:
- QUERY_CHART_DATA: series rejected (expected array, received string) — 6+ failures
- GET_LOG_DETAILS: groupBy rejected (expected array, received string) — 2-3 failures
- SEARCH_LOGS: limit rejected (expected number, received string)
Add a small coerce helper (arr() / num()) and wrap every array and number
input field across the HyperDX tools so they accept either the raw type or
a JSON/numeric string. Mirrors the same pattern already in
vtex/server/tools/custom/reorder-collection.ts.
Adds unit tests for the helper and the queryChartDataInputSchema.
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
"Global filter applied to all charts on the dashboard (e.g., 'env:production').",
130
131
),
131
-
tags: z
132
-
.array(z.string())
133
-
.optional()
134
-
.default([])
135
-
.describe("Organizational tags for the dashboard."),
136
-
charts: z
137
-
.array(DashboardChartSchema)
138
-
.describe(
139
-
"Array of charts to include. Each chart needs a name, grid position (x/y/w/h), and series. Charts are placed on a grid — typical width is 12 units total.",
"Array of charts to include. Each chart needs a name, grid position (x/y/w/h), and series. Charts are placed on a grid — typical width is 12 units total.",
0 commit comments