@xano/developer-mcp 1.0.26 → 1.0.28

package/dist/xanoscript_docs/tables.md

@@ -23,9 +23,11 @@ table "<name>" {
 ```
 
 ### Field Types
+
 `int`, `text`, `email`, `password`, `decimal`, `bool`, `timestamp`, `date`, `uuid`, `vector`, `json`, `image`, `video`, `audio`, `attachment`, `enum`
 
 ### Index Types
+
 `primary`, `btree`, `btree|unique`, `gin`
 
 ---
@@ -58,6 +60,7 @@ table "user" {
 ## Schema Fields
 
 ### Basic Fields
+
 ```xs
 schema {
   int id
@@ -70,6 +73,7 @@ schema {
 ```
 
 ### Optional & Defaults
+
 ```xs
 schema {
   text nickname?                   // Optional, no default
@@ -80,6 +84,7 @@ schema {
 ```
 
 ### With Filters
+
 ```xs
 schema {
   text name filters=trim
@@ -90,6 +95,7 @@ schema {
 ```
 
 ### With Metadata
+
 ```xs
 schema {
   text ssn {
@@ -104,6 +110,7 @@ schema {
 ```
 
 ### Foreign Keys
+
 ```xs
 schema {
   int user_id {
@@ -117,6 +124,7 @@ schema {
 ```
 
 ### Enum Fields
+
 ```xs
 schema {
   enum status {
@@ -129,6 +137,7 @@ schema {
 ```
 
 ### JSON Fields
+
 ```xs
 schema {
   json metadata
@@ -137,17 +146,24 @@ schema {
 ```
 
 ### Vector Fields
+
 ```xs
 schema {
-  vector embedding              // For AI/ML embeddings
+  vector embedding              // Required vector field
+  vector? embeddings? {         // Optional vector field with explicit size
+    size = 768
+  }
 }
 ```
 
+The `size` parameter specifies the vector dimensions (must match your embedding model's output). Pair with a vector index for similarity search (see [Vector Index](#vector-index) below).
+
 ---
 
 ## Indexes
 
 ### Primary Key
+
 ```xs
 index = [
   {type: "primary", field: [{name: "id"}]}
@@ -155,6 +171,7 @@ index = [
 ```
 
 ### B-tree Index
+
 ```xs
 index = [
   {type: "btree", field: [{name: "email", op: "asc"}]}
@@ -163,6 +180,7 @@ index = [
 ```
 
 ### Unique Index
+
 ```xs
 index = [
   {type: "btree|unique", field: [{name: "email"}]}
@@ -171,6 +189,7 @@ index = [
 ```
 
 ### Composite Index
+
 ```xs
 index = [
   {type: "btree", field: [{name: "user_id"}, {name: "created_at", op: "desc"}]}
@@ -178,6 +197,7 @@ index = [
 ```
 
 ### GIN Index (for JSON/arrays)
+
 ```xs
 index = [
   {type: "gin", field: [{name: "tags", op: "jsonb_path_op"}]}
@@ -185,11 +205,35 @@ index = [
 ]
 ```
 
+### Full-Text Search Index
+
+```xs
+index = [
+  {
+    name : "search_content"
+    lang : "english"
+    type : "search"
+    field: [{name: "searchable_content", op: "A"}]
+  }
+]
+```
+
+### Vector Index
+
+```xs
+index = [
+  {type: "vector", field: [{name: "embeddings", op: "vector_cosine_ops"}]}
+]
+```
+
+Required for vector similarity searches via `cosine_distance` in `db.query`. PostgreSQL vector indexes only support ascending scans, so queries must sort by distance `asc` to use the index. Sorting `desc` will bypass the index and trigger a full table scan. See [database.md](database.md) for query usage.
+
 ---
 
 ## Complete Examples
 
 ### User Table (with auth)
+
 ```xs
 table "user" {
   auth = true
@@ -212,6 +256,7 @@ table "user" {
 ```
 
 ### Product Table
+
 ```xs
 table "product" {
   auth = false
@@ -235,6 +280,7 @@ table "product" {
 ```
 
 ### Order with Foreign Keys
+
 ```xs
 table "order" {
   auth = false

package/dist/xanoscript_docs/tools.md

@@ -74,25 +74,6 @@ input {
 }
 ```
 
-### Empty Input Blocks
-
-**CRITICAL:** When a tool has no input parameters, the input block braces MUST be on separate lines. `input {}` on a single line will cause parsing errors.
-
-```xs
-// CORRECT - braces on separate lines
-tool "get_system_status" {
-  description = "Get current system status"
-  instructions = "Use this to check if the system is healthy"
-  input {
-  }
-  stack { ... }
-  response = $status
-}
-
-// WRONG - causes parsing errors
-input {}
-```
-
 ---
 
 ## Tool-Specific Statements
@@ -273,6 +254,8 @@ tool "get_order_with_items" {
 
 ## Error Handling
 
+For complete error handling reference (preconditions, try-catch, throw, error types), see `xanoscript_docs({ topic: "syntax" })`.
+
 ```xs
 tool "cancel_order" {
   instructions = "Cancel an order. Only works for pending orders."

package/dist/xanoscript_docs/triggers.md

@@ -43,34 +43,9 @@ input {
 | `action` | enum | The action that triggered: `insert`, `update`, `delete`, or `truncate` |
 | `datasource` | text | The datasource name where the change occurred |
 
-### Agent Trigger Input
+### Agent Trigger Input / MCP Server Trigger Input
 
-```xs
-input {
-  object toolset {
-    schema {
-      int id
-      text name
-      text instructions
-    }
-  }
-
-  object[] tools {
-    schema {
-      int id
-      text name
-      text instructions
-    }
-  }
-}
-```
-
-| Field | Type | Description |
-|-------|------|-------------|
-| `toolset` | object | The toolset configuration with id, name, and instructions |
-| `tools` | object[] | Array of available tools with their id, name, and instructions |
-
-### MCP Server Trigger Input
+Agent triggers and MCP server triggers share the same input schema:
 
 ```xs
 input {

package/dist/xanoscript_docs/types.md

@@ -60,23 +60,25 @@ input {
 }
 ```
 
-### Empty Input Blocks
+### Empty and Single-Input Blocks
 
-**SYNTAX REQUIREMENT:** When an input block has no parameters, the braces MUST be on separate lines.
+Empty input blocks and single-input blocks can be written as one-liners. When there are two or more inputs, each must be on its own line.
 
-**Why:** The XanoScript parser requires whitespace between braces to distinguish empty input blocks from inline objects.
+```xs
+// OK - empty input as one-liner
+input {}
 
-**Impact:** Using `input {}` on a single line will cause:
-- Syntax error during compilation
-- Function/API/tool will fail to deploy
+// OK - single input as one-liner
+input { email email_input? filters=trim|lower }
 
-```xs
-// CORRECT - braces on separate lines
+// OK - multiple inputs on separate lines
 input {
+  email email_input? filters=trim|lower
+  text name
 }
 
-// WRONG - causes parsing errors
-input {}
+// WRONG - multiple inputs on one line will cause parsing errors
+input { email email_input? filters=trim|lower text name }
 ```
 
 Access inputs in stack: `$input.username`, `$input.age`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@xano/developer-mcp",
-  "version": "1.0.26",
+  "version": "1.0.28",
   "description": "MCP server for Xano Headless API documentation and XanoScript code validation",
   "type": "module",
   "main": "dist/index.js",