mc8yp 2.2.1 → 2.2.2

package/dist/cli.mjs

@@ -41,7 +41,7 @@ var __require = /* @__PURE__ */ createRequire(import.meta.url);
 //#endregion
 //#region package.json
 var name = "mc8yp";
-var version = "2.2.1";
+var version = "2.2.2";
 var description = "Cumulocity IoT MCP Server - Model Context Protocol integration for IoT device management";
 //#endregion
 //#region \0virtual:core-openapi
@@ -93139,8 +93139,9 @@ You have exactly two MCP tools available.
 ## query
 Use \`query\` when you need to inspect the bundled OpenAPI specs.
 
-- Input: a JavaScript function expression
-- The top-level bindings \`coreSpec\`, \`dtmSpec\`, and \`specsEnabled\` are available automatically
+- Input: a **zero-parameter** JavaScript function expression
+- Do NOT declare \`coreSpec\`, \`dtmSpec\`, or \`specsEnabled\` as function parameters — they are already declared as top-level constants in the surrounding scope. Writing \`(dtmSpec) => ...\` would shadow the global with an undefined parameter and produce incorrect results
+- The top-level bindings \`coreSpec\`, \`dtmSpec\`, and \`specsEnabled\` are available automatically inside the function body
 - \`coreSpec\` is for the main Cumulocity REST surface such as inventory, alarms, events, measurements, identity, device control, users, tenants, audit, and the broader platform APIs
 - \`dtmSpec\` is for Digital Twin Manager work such as schema definitions, asset models, linked series, and DTM asset or definition APIs
 - Return the exact value you want back from that function
@@ -93150,6 +93151,9 @@ Use \`query\` when you need to inspect the bundled OpenAPI specs.
 - The current MCP connection may still block \`execute\` requests through deny rules and/or an allow list even when an operation exists in a visible spec
 
 ### Available Shape
+
+The function must accept **no parameters**. The bindings below are scope-level constants, not function arguments.
+
 \`\`\`ts
 type OperationInfo = {
   summary?: string
@@ -93186,7 +93190,7 @@ declare const dtmSpec: DtmSpec
 declare const specsEnabled: SpecsEnabled
 \`\`\`
 
-Examples:
+Examples (all zero-parameter — note no arguments in the arrow function signatures):
 \`\`\`js
 () => specsEnabled
 \`\`\`
@@ -93197,6 +93201,7 @@ Examples:
 
 \`\`\`js
 () => {
+  // dtmSpec is already in scope — do NOT write (dtmSpec) => { ... }
   const op = dtmSpec.paths['/assets']?.get
   return op?.parameters
 }
@@ -150867,7 +150872,9 @@ declare const coreSpec: CoreSpec
 declare const dtmSpec: DtmSpec
 declare const specsEnabled: SpecsEnabled
 
-Your code must evaluate to a function. The top-level bindings \
+Your code must evaluate to a **zero-parameter** function — do NOT declare \`coreSpec\`, \`dtmSpec\`, or \`specsEnabled\` as function parameters. These are already declared as constants in the surrounding scope and are available inside the function body without any argument passing. Writing \`(dtmSpec) => ...\` would shadow the global binding with an undefined parameter and produce incorrect results.
+
+The top-level bindings \
 
 a) \`coreSpec\` — use this for the main Cumulocity REST APIs such as inventory, alarms, events, measurements, identity, device control, users, tenants, audit, and the broader platform REST surface
 \nb) \`dtmSpec\` — use this for Digital Twin Manager work such as schema definitions, asset models, linked series, and DTM asset or definition APIs
@@ -150875,7 +150882,7 @@ a) \`coreSpec\` — use this for the main Cumulocity REST APIs such as inventory
 
 are available automatically. The sandbox assigns your function to a local variable, invokes it, and returns its result.
 
-Recommended shapes:
+Recommended shapes (zero parameters — bindings come from scope, not arguments):
 \`(() => { ... })\`
 \`async () => { ... }\`
 
@@ -150910,7 +150917,7 @@ Examples:
   return { summary: op?.summary, parameters: op?.parameters, responses: op?.responses }
 }
 `,
-		schema: v.object({ code: createCodeSchema("A JavaScript function expression. The top-level bindings `coreSpec`, `dtmSpec`, and `specsEnabled` are available automatically. Return the final result from that function. Async functions are supported.") })
+		schema: v.object({ code: createCodeSchema("A zero-parameter JavaScript function expression. Do NOT declare `coreSpec`, `dtmSpec`, or `specsEnabled` as function parameters — they are already declared as top-level constants in the surrounding scope and are available in the function body automatically. Writing `(dtmSpec) => ...` would shadow the global binding with an undefined parameter and produce incorrect results. Return the final result from that function. Async functions are supported.") })
 	}, async (input) => {
 		try {
 			return tool.text(await query(input.code, server.ctx.custom?.restrictions ?? [], server.ctx.custom?.allowRules ?? [], server.ctx.custom?.disabledApis ?? []));

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mc8yp",
-  "version": "2.2.1",
+  "version": "2.2.2",
   "type": "module",
   "description": "Cumulocity IoT MCP Server - Model Context Protocol integration for IoT device management",
   "keywords": [