@thehammer/danx-dashboard-mcp 0.1.242 → 0.1.243

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -125,11 +125,8 @@ export class DashboardHttpClient {
125
125
  // JSON. Arrays are `typeof "object"` too, so the array check must
126
126
  // come BEFORE the plain-object branch. A plain scalar stringifies
127
127
  // as before.
128
- // DX-4405 — an array holding an object (the list `sort`) is the one array the server parses as JSON.
129
128
  params.set(k, Array.isArray(v)
130
- ? v.some((item) => typeof item === "object")
131
- ? JSON.stringify(v)
132
- : v.map((item) => String(item)).join(",")
129
+ ? v.map((item) => String(item)).join(",")
133
130
  : typeof v === "object"
134
131
  ? JSON.stringify(v)
135
132
  : String(v));
package/dist/index.js CHANGED
@@ -433,11 +433,11 @@ strictTool("danxbot_api",
433
433
  // DX-3465 — a query value may be a scalar, a field TREE (a plain
434
434
  // object, e.g. `{"description":true,"comments":{"limit":20}}` — see
435
435
  // SERVER_INSTRUCTIONS above and the OpenAPI spec's `fields` schema), an
436
- // array of scalars (e.g. `ids` on the batch-get route) or, DX-4405, an
437
- // array of objects (a list's `sort`, `[{column, order}]`).
438
- // `DashboardHttpClient#buildUrl` JSON-encodes a plain object and an array
439
- // of objects but comma-joins an array of scalars, matching the shapes the
440
- // server actually parses (a JSON tree or sort vs. a comma-separated list param).
436
+ // array of scalars (e.g. `ids` on the batch-get route); a list's sort is
437
+ // two scalars, `sort` + `order` (DX-4492).
438
+ // `DashboardHttpClient#buildUrl` JSON-encodes a plain object but
439
+ // comma-joins an array, matching the shapes the server actually parses
440
+ // (a JSON tree vs. a comma-separated list param).
441
441
  query: queryValueSchema.optional(),
442
442
  // DX-3685 — was `z.unknown()` (JSON Schema `{}`), which gave the model
443
443
  // no structural hint that a body must be an OBJECT, so it sometimes
package/dist/types.js CHANGED
@@ -2,7 +2,7 @@ import { z } from "zod";
2
2
  /**
3
3
  * The zod schema for `danxbot_api`'s `query` argument, matching the
4
4
  * `QueryValue` type above — a scalar, a field-tree object, or an array of
5
- * scalars (comma-joined) or objects (JSON-encoded, the list `sort`). Exported so it can be exercised
5
+ * scalars (comma-joined). Exported so it can be exercised
6
6
  * directly in tests without going through the MCP tool-call machinery.
7
7
  */
8
8
  export const queryValueSchema = z.record(z.union([
@@ -11,7 +11,7 @@ export const queryValueSchema = z.record(z.union([
11
11
  z.boolean(),
12
12
  z.null(),
13
13
  z.record(z.unknown()),
14
- z.array(z.union([z.string(), z.number(), z.boolean(), z.record(z.unknown())])),
14
+ z.array(z.union([z.string(), z.number(), z.boolean()])),
15
15
  ]));
16
16
  /**
17
17
  * DX-3685 — the zod schema for `danxbot_api`'s `body` argument. Every
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@thehammer/danx-dashboard-mcp",
3
- "version": "0.1.242",
3
+ "version": "0.1.243",
4
4
  "description": "Stdio MCP server fronting danxbot's dashboard API for agents (operator sessions and dispatched workers alike): the generic danxbot_api/danxbot_api_list/danxbot_api_spec tools reach any route the caller's credential may call, plus dedicated agent-specific tools (plan_connect, danxbot_complete, and other per-dispatch lifecycle callbacks) (DX-3465, PLN-11 R-25).",
5
5
  "license": "MIT",
6
6
  "type": "module",