@xano/developer-mcp 1.0.44 → 1.0.46

package/dist/xanoscript_docs/cheatsheet.md

@@ -228,10 +228,14 @@ var $msg { value = ($status|to_text) ~ ": " ~ ($data|json_encode) }
 
 ## Input Block Syntax
 
+`?` after the **type** = nullable, `?` after the **variable name** = optional (not required).
+
 ```xs
 input {
-  text name                    // Required
-  text nickname?               // Optional (can be omitted)
+  text name                    // Required, not nullable
+  text? name                   // Required, nullable (can send null)
+  text name?                   // Optional (can be omitted)
+  text? name?                  // Optional and nullable
   text role?="user"            // Optional with default
   email contact filters=trim   // With filters
   text[] tags                  // Array type

package/dist/xanoscript_docs/functions.md

@@ -83,10 +83,14 @@ Reference with path: `function.run "math/add" { ... }`
 
 For complete type and filter reference, use `xanoscript_docs({ topic: "types" })`.
 
+`?` after the **type** = nullable (`text?`), `?` after the **variable name** = not required (`age?`).
+
 ```xs
 input {
-  text name filters=trim
-  int age? filters=min:0
+  text name filters=trim                          // Required, not nullable
+  text? bio filters=trim                          // Required, nullable
+  int age? filters=min:0                          // Optional (not required)
+  text? nickname? filters=trim                    // Optional and nullable
   email contact filters=lower { sensitive = true }
 }
 ```

package/dist/xanoscript_docs/quickstart.md

@@ -172,13 +172,23 @@ var $message { value = "Status: " ~ ($status|to_text) ~ " - " ~ ($data|json_enco
 
 > **Full reference:** For complete input types and validation options, see `xanoscript_docs({ topic: "types" })`.
 
+The `?` has different meanings depending on placement:
+- **After the type** (`text?`) → **nullable** (value can be `null`)
+- **After the variable name** (`name?`) → **not required** (optional)
+
 ```xs
 input {
-  // Required input
+  // Required, not nullable
   text name
 
-  // Optional input (can be omitted)
-  text nickname?
+  // Required, nullable (caller must provide, but can send null)
+  text? name
+
+  // Optional, not nullable (can be omitted, but if sent must have value)
+  text name?
+
+  // Optional AND nullable (can be omitted or sent as null)
+  text? name?
 
   // Optional with default value
   text role?="user"
@@ -186,9 +196,6 @@ input {
   // With filters applied
   email contact filters=trim|lower
 
-  // Optional with default AND filters
-  text search?="" filters=trim
-
   // Array type
   text[] tags filters=trim
 

package/dist/xanoscript_docs/types.md

@@ -6,7 +6,7 @@ applyTo: "function/**/*.xs, api/**/*.xs, tool/**/*.xs, agent/**/*.xs"
 
 Reference for XanoScript data types, input blocks, and validation.
 
-> **TL;DR:** Use `text` not `string`, `int` not `integer`, `bool` not `boolean`. Add `?` for nullable, `?=value` for defaults. Use `filters=` for validation. Arrays use `type[]` syntax.
+> **TL;DR:** Use `text` not `string`, `int` not `integer`, `bool` not `boolean`. `?` after the **type** = nullable (`text?`), `?` after the **variable name** = optional/not required (`name?`). Use `filters=` for validation. Arrays use `type[]` syntax.
 
 ---
 
@@ -36,13 +36,21 @@ Reference for XanoScript data types, input blocks, and validation.
 | `geo_point` / `geo_polygon` / `geo_linestring` | Geographic data |
 
 ### Modifiers
-| Syntax | Meaning |
-|--------|---------|
-| `text?` | Nullable (can be null) |
-| `text name?` | Optional (not required) |
-| `text name?="default"` | Optional with default |
-| `text[]` | Array of type |
-| `text[1:10]` | Array with size constraints |
+
+The `?` has different meanings depending on placement:
+
+- **After the type** (`text?`) → the value is **nullable** (can be `null`)
+- **After the variable name** (`name?`) → the value is **not required** (optional)
+
+| Syntax | Nullable | Required | Description |
+|--------|----------|----------|-------------|
+| `text name` | No | Yes | Required, cannot be null |
+| `text? name` | Yes | Yes | Required, can be null |
+| `text name?` | No | No | Optional, cannot be null |
+| `text? name?` | Yes | No | Optional, can be null |
+| `text name?="default"` | No | No | Optional with default value |
+| `text[]` | — | — | Array of type |
+| `text[1:10]` | — | — | Array with size constraints |
 
 ---
 
@@ -291,22 +299,29 @@ input {
 
 ## Nullable vs Optional
 
+The `?` marker controls two independent behaviors based on where it's placed:
+
+- **`?` after the type** (e.g., `text?`) → **nullable**: the value can be `null`
+- **`?` after the variable name** (e.g., `name?`) → **not required**: the caller can omit the field entirely
+
+These combine to form four distinct behaviors:
+
 ```xs
 input {
-  // Required, cannot be null
-  text required_field
+  // Required, cannot be null — caller MUST provide a non-null value
+  text name filters=trim
 
-  // Required, can be null (must provide, can send null)
-  text? nullable_field
+  // Required, CAN be null — caller MUST provide the field, but can send null
+  text? name filters=trim
 
-  // Optional, cannot be null (can omit, but if sent must have value)
-  text optional_field?
+  // Optional, cannot be null — caller can omit, but if sent must have a value
+  text name? filters=trim
 
-  // Optional, can be null (can omit or send null)
-  text? nullable_optional?
+  // Optional, CAN be null — caller can omit or send null
+  text? name? filters=trim
 
-  // Optional with default
-  text with_default?="hello"
+  // Optional with default — if omitted, uses the default value
+  text name?="hello"
 }
 ```
 

package/dist/xanoscript_docs/workflow-tests.md

@@ -55,6 +55,8 @@ addon.call "<addon_name>" as $result
 
 ### function.call
 
+> **Important:** Always use `function.call` in workflow tests, not `function.run`. `function.call` handles errors internally, which is required for `expect` assertions (such as `expect.to_throw`) to work correctly. `function.run` is for calling functions from other primitives (APIs, functions, tasks, etc.) outside of workflow tests.
+
 ```xs
 function.call "<function_name>" {
   input = { key: "value" }
@@ -319,7 +321,8 @@ workflow_test "comprehensive_test" {
 2. **Tag for filtering** — Use tags like `critical`, `e2e`, `smoke` to organize test suites
 3. **Avoid `datasource = "live"`** — The entire datasource is cloned before each test run, which can be slow. Use no datasource or a smaller custom datasource instead
 4. **Keep tests independent** — Each workflow test should be self-contained and not depend on other tests
-5. **Use assertions over preconditions** — Prefer `expect.*` assertions for clearer test intent
+5. **Use `function.call`, not `function.run`** — `function.call` handles errors so that `expect` assertions work correctly. `function.run` is for calling functions outside of workflow tests
+6. **Use assertions over preconditions** — Prefer `expect.*` assertions for clearer test intent
 
 ---
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@xano/developer-mcp",
-  "version": "1.0.44",
+  "version": "1.0.46",
   "description": "MCP server and library for Xano development - XanoScript validation, Meta API, Run API, and CLI documentation",
   "type": "module",
   "main": "dist/lib.js",