@xano/developer-mcp 1.0.5 → 1.0.7

package/xanoscript_docs/functions.md

@@ -15,7 +15,7 @@ function "<name>" {
     <type> <name> [filters=...] { description = "..." }
   }
   stack {
-    # Logic here
+    // Logic here
   }
   response = $result
 }
@@ -63,20 +63,13 @@ Reference with path: `function.run "math/add" { ... }`
 
 ## Input Block
 
-See [types.md](types.md) for complete type reference.
+For complete type and filter reference, use `xanoscript_docs({ keyword: "input" })`.
 
 ```xs
 input {
   text name filters=trim
   int age? filters=min:0
   email contact filters=lower { sensitive = true }
-  object address? {
-    schema {
-      text street
-      text city
-      text zip
-    }
-  }
 }
 ```
 
@@ -117,21 +110,21 @@ stack {
 ### Loops
 ```xs
 stack {
-  # For loop (count-based)
+  // For loop (count-based)
   for (10) {
     each as $i {
       debug.log { value = $i }
     }
   }
 
-  # Foreach (array iteration)
+  // Foreach (array iteration)
   foreach ($input.items) {
     each as $item {
       debug.log { value = $item.name }
     }
   }
 
-  # While loop
+  // While loop
   while ($counter < 5) {
     each {
       math.add $counter { value = 1 }
@@ -158,49 +151,8 @@ stack {
 ```
 
 ### Error Handling
-```xs
-stack {
-  try_catch {
-    try {
-      function.run "risky_operation" { input = {} } as $result
-    }
-    catch {
-      debug.log { value = "Operation failed" }
-      var $result { value = null }
-    }
-    finally {
-      debug.log { value = "Cleanup complete" }
-    }
-  }
-}
-```
 
-### Throwing Errors
-```xs
-stack {
-  precondition ($input.amount > 0) {
-    error_type = "inputerror"
-    error = "Amount must be positive"
-  }
-
-  throw {
-    name = "ValidationError"
-    value = "Custom error message"
-  }
-}
-```
-
-### Early Return
-```xs
-stack {
-  conditional {
-    if ($input.skip) {
-      return { value = null }
-    }
-  }
-  # Continue processing...
-}
-```
+For complete error handling reference (preconditions, try-catch, throw, early return), use `xanoscript_docs({ keyword: "syntax" })`.
 
 ---
 
@@ -209,10 +161,10 @@ stack {
 Specify what the function returns:
 
 ```xs
-response = $total                    # Single variable
-response = { success: true, data: $result }   # Object literal
-response = $items|first              # With filter
-response = null                      # No return value
+response = $total                    // Single variable
+response = { success: true, data: $result }   // Object literal
+response = $items|first              // With filter
+response = null                      // No return value
 ```
 
 ---
@@ -345,8 +297,5 @@ function "validate_email_unique" {
 1. **Single responsibility** - Each function does one thing well
 2. **Descriptive names** - Use verb_noun format: `calculate_total`, `validate_user`
 3. **Organize in folders** - Group related functions: `utils/`, `auth/`, `orders/`
-4. **Validate inputs** - Use filters and preconditions
-5. **Handle errors** - Use try_catch for external calls
-6. **Document purpose** - Add description field
-7. **Return early** - Use return for guard clauses
-8. **Keep stacks shallow** - Avoid deeply nested conditionals
+4. **Return early** - Use return for guard clauses
+5. **Keep stacks shallow** - Avoid deeply nested conditionals

package/xanoscript_docs/integrations.md

@@ -182,20 +182,20 @@ cloud.elasticsearch.document {
 
 ### Key-Value Operations
 ```xs
-# Set value
+// Set value
 redis.set {
   key = "user:123:session"
   data = $session_data
-  ttl = 3600                            # Expires in 1 hour
+  ttl = 3600                            // Expires in 1 hour
 }
 
-# Get value
+// Get value
 redis.get { key = "user:123:session" } as $session
 
-# Check exists
+// Check exists
 redis.has { key = "user:123:session" } as $exists
 
-# Delete
+// Delete
 redis.del { key = "user:123:session" }
 ```
 

package/xanoscript_docs/mcp-servers.md

@@ -147,18 +147,18 @@ mcp_server "CRM" {
 ### By Domain
 ```
 mcp_servers/
-├── support.xs          # Customer support tools
-├── ecommerce.xs        # Store management
-├── analytics.xs        # Reporting and metrics
-└── admin.xs            # Administrative functions
+├── support.xs          // Customer support tools
+├── ecommerce.xs        // Store management
+├── analytics.xs        // Reporting and metrics
+└── admin.xs            // Administrative functions
 ```
 
 ### By Access Level
 ```
 mcp_servers/
-├── public.xs           # Public-facing tools
-├── authenticated.xs    # Requires auth
-└── admin.xs            # Admin-only tools
+├── public.xs           // Public-facing tools
+├── authenticated.xs    // Requires auth
+└── admin.xs            // Admin-only tools
 ```
 
 ---
@@ -182,9 +182,6 @@ The MCP protocol handles:
 ## Best Practices
 
 1. **Clear naming** - Server name should indicate its purpose
-2. **Memorable canonical IDs** - Use descriptive, stable identifiers
-3. **Comprehensive instructions** - Guide AI on server's overall purpose
-4. **Logical tool grouping** - Group related tools in one server
-5. **Use tags** - Organize servers by category
-6. **Keep focused** - One domain per server (support, analytics, etc.)
-7. **Document internally** - Use description for team documentation
+2. **Comprehensive instructions** - Guide AI on server's overall purpose
+3. **Logical tool grouping** - Group related tools in one server
+4. **Keep focused** - One domain per server (support, analytics, etc.)

package/xanoscript_docs/syntax.md

@@ -44,24 +44,24 @@ var $total { value = `$input.qty * $input.price` }
 
 ### Comparison
 ```xs
-$a == $b      # Equal
-$a != $b      # Not equal
-$a > $b       # Greater than
-$a >= $b      # Greater or equal
-$a < $b       # Less than
-$a <= $b      # Less or equal
+$a == $b      // Equal
+$a != $b      // Not equal
+$a > $b       // Greater than
+$a >= $b      // Greater or equal
+$a < $b       // Less than
+$a <= $b      // Less or equal
 ```
 
 ### Logical
 ```xs
-$a && $b      # AND
-$a || $b      # OR
-!$a           # NOT
+$a && $b      // AND
+$a || $b      // OR
+!$a           // NOT
 ```
 
 ### Null-Safe Comparisons (DB Queries)
 ```xs
-# In db.query where clauses - ignore condition if value is null
+// In db.query where clauses - ignore condition if value is null
 $db.post.category ==? $input.category
 $db.post.date >=? $input.start_date
 ```
@@ -88,11 +88,11 @@ $db.post.date >=? $input.start_date
 
 ### Array Math
 ```xs
-[1,2,3,4]|sum        # 10
-[1,2,3,4]|avg        # 2.5
-[1,2,3,4]|product    # 24
-[5,2,8,1]|array_min  # 1
-[5,2,8,1]|array_max  # 8
+[1,2,3,4]|sum        // 10
+[1,2,3,4]|avg        // 2.5
+[1,2,3,4]|product    // 24
+[5,2,8,1]|array_min  // 1
+[5,2,8,1]|array_max  // 8
 ```
 
 ### Trigonometry
@@ -123,10 +123,10 @@ $db.post.date >=? $input.start_date
 
 ### Regex
 ```xs
-"/pattern/"|regex_matches:"subject"           # Boolean match
-"/(\w+)/"|regex_get_first_match:"test"        # First match
-"/\w+/"|regex_get_all_matches:"a b c"         # All matches
-"/\s+/"|regex_replace:"-":"a  b"              # Replace: "a-b"
+"/pattern/"|regex_matches:"subject"           // Boolean match
+"/(\w+)/"|regex_get_first_match:"test"        // First match
+"/\w+/"|regex_get_all_matches:"a b c"         // All matches
+"/\s+/"|regex_replace:"-":"a  b"              // Replace: "a-b"
 ```
 
 ---
@@ -155,36 +155,36 @@ $db.post.date >=? $input.start_date
 
 ### Functional Operations
 ```xs
-# Map - transform each element
-[{v:1},{v:2}]|map:$$.v*2                    # [2,4]
+// Map - transform each element
+[{v:1},{v:2}]|map:$$.v*2                    // [2,4]
 
-# Filter - keep matching elements
-[1,2,3,4]|filter:$$%2==0                    # [2,4]
+// Filter - keep matching elements
+[1,2,3,4]|filter:$$%2==0                    // [2,4]
 
-# Find - first matching element
-[{id:1},{id:2}]|find:$$.id==2               # {id:2}
+// Find - first matching element
+[{id:1},{id:2}]|find:$$.id==2               // {id:2}
 
-# FindIndex - index of first match
-[{id:1},{id:2}]|findIndex:$$.id==2          # 1
+// FindIndex - index of first match
+[{id:1},{id:2}]|findIndex:$$.id==2          // 1
 
-# Some - any element matches?
-[1,2,3]|some:$$>2                           # true
+// Some - any element matches?
+[1,2,3]|some:$$>2                           // true
 
-# Every - all elements match?
-[2,4,6]|every:$$%2==0                       # true
+// Every - all elements match?
+[2,4,6]|every:$$%2==0                       // true
 
-# Reduce - accumulate to single value
-[1,2,3,4]|reduce:$$+$result:0               # 10
+// Reduce - accumulate to single value
+[1,2,3,4]|reduce:$$+$result:0               // 10
 ```
 
 ### Grouping & Indexing
 ```xs
-# Group by property
+// Group by property
 [{g:"a",v:1},{g:"b",v:2},{g:"a",v:3}]|index_by:g
-# {"a":[{g:"a",v:1},{g:"a",v:3}],"b":[{g:"b",v:2}]}
+// {"a":[{g:"a",v:1},{g:"a",v:3}],"b":[{g:"b",v:2}]}
 
-# Sort
-[{n:"z"},{n:"a"}]|sort:n:text:false         # Ascending by n
+// Sort
+[{n:"z"},{n:"a"}]|sort:n:text:false         // Ascending by n
 ```
 
 ---
@@ -205,9 +205,9 @@ $db.post.date >=? $input.start_date
 
 ### Conditional Set
 ```xs
-{a:1}|set_conditional:"b":2:true            # {a:1,b:2} if condition true
-{a:1}|set_ifnotempty:"b":"val"              # Set only if val not empty
-{a:1}|set_ifnotnull:"b":$var                # Set only if $var not null
+{a:1}|set_conditional:"b":2:true            // {a:1,b:2} if condition true
+{a:1}|set_ifnotempty:"b":"val"              // Set only if val not empty
+{a:1}|set_ifnotnull:"b":$var                // Set only if $var not null
 ```
 
 ---
@@ -229,8 +229,8 @@ $db.post.date >=? $input.start_date
 
 ### Null Handling
 ```xs
-null|first_notnull:0                        # 0
-""|first_notempty:"default"                 # "default"
+null|first_notnull:0                        // 0
+""|first_notempty:"default"                 // "default"
 ```
 
 ---
@@ -249,12 +249,12 @@ null|first_notnull:0                        # 0
 
 ### Timestamp Parts
 ```xs
-$ts|timestamp_year           # Year
-$ts|timestamp_month          # Month (1-12)
-$ts|timestamp_day_of_month   # Day (1-31)
-$ts|timestamp_hour           # Hour (0-23)
-$ts|timestamp_minute         # Minute (0-59)
-$ts|timestamp_day_of_week    # Day (0=Sunday)
+$ts|timestamp_year           // Year
+$ts|timestamp_month          // Month (1-12)
+$ts|timestamp_day_of_month   // Day (1-31)
+$ts|timestamp_hour           // Hour (0-23)
+$ts|timestamp_minute         // Minute (0-59)
+$ts|timestamp_day_of_week    // Day (0=Sunday)
 ```
 
 ---
@@ -312,3 +312,73 @@ Used in `db.query` where clauses:
 $db.created_at|timestamp_add_days:7
 $db.created_at|timestamp_subtract_hours:24
 ```
+
+---
+
+## Error Handling
+
+### Preconditions
+
+Validate conditions and throw typed errors:
+
+```xs
+precondition ($input.amount > 0) {
+  error_type = "inputerror"
+  error = "Amount must be positive"
+}
+
+precondition ($user != null) {
+  error_type = "notfound"
+  error = "User not found"
+}
+
+precondition ($user.id == $auth.id) {
+  error_type = "accessdenied"
+  error = "Not authorized"
+}
+```
+
+### Error Types
+
+| Type | HTTP Status | Use Case |
+|------|-------------|----------|
+| `inputerror` | 400 Bad Request | Invalid input data |
+| `accessdenied` | 403 Forbidden | Authorization failure |
+| `notfound` | 404 Not Found | Resource doesn't exist |
+| `standard` | 500 Internal Server Error | General errors |
+
+### Throwing Errors
+
+```xs
+throw {
+  name = "ValidationError"
+  value = "Custom error message"
+}
+```
+
+### Try-Catch
+
+```xs
+try_catch {
+  try {
+    function.run "risky_operation" { input = {} } as $result
+  }
+  catch {
+    debug.log { value = "Operation failed" }
+    var $result { value = null }
+  }
+  finally {
+    debug.log { value = "Cleanup complete" }
+  }
+}
+```
+
+### Early Return
+
+```xs
+conditional {
+  if ($input.skip) {
+    return { value = null }
+  }
+}
+```

package/xanoscript_docs/tables.md

@@ -10,9 +10,9 @@ Database table definitions in XanoScript.
 
 ```xs
 table "<name>" {
-  auth = false                    # true if used for authentication
+  auth = false                    // true if used for authentication
   schema {
-    int id                        # Primary key (required)
+    int id                        // Primary key (required)
     text name filters=trim
     timestamp created_at?=now
   }
@@ -72,10 +72,10 @@ schema {
 ### Optional & Defaults
 ```xs
 schema {
-  text nickname?                   # Optional, no default
-  timestamp created_at?=now        # Optional, defaults to current time
-  bool is_active?=true             # Optional, defaults to true
-  int status?=0                    # Optional, defaults to 0
+  text nickname?                   // Optional, no default
+  timestamp created_at?=now        // Optional, defaults to current time
+  bool is_active?=true             // Optional, defaults to true
+  int status?=0                    // Optional, defaults to 0
 }
 ```
 
@@ -139,7 +139,7 @@ schema {
 ### Vector Fields
 ```xs
 schema {
-  vector embedding              # For AI/ML embeddings
+  vector embedding              // For AI/ML embeddings
 }
 ```
 
@@ -264,7 +264,4 @@ table "order" {
 2. **Use `auth = true`** only for authentication tables (typically just `user`)
 3. **Add indexes** for fields used in WHERE clauses and JOINs
 4. **Use appropriate types** - `email` for emails, `password` for credentials
-5. **Mark sensitive fields** - Set `sensitive = true` for PII
-6. **Use filters** - Apply `trim`, `lower` for consistency
-7. **Default timestamps** - Use `?=now` for created_at fields
-8. **Document with descriptions** - Add descriptions for non-obvious fields
+5. **Default timestamps** - Use `?=now` for created_at fields

package/xanoscript_docs/tasks.md

@@ -222,7 +222,7 @@ task "risky_sync" {
           url = "https://external-api.com/data"
           method = "GET"
         } as $data
-        # Process data...
+        // Process data...
       }
       catch {
         util.send_email {
@@ -244,11 +244,8 @@ task "risky_sync" {
 
 ## Best Practices
 
-1. **Use descriptive names** - Indicate what and when: `daily_cleanup`, `hourly_sync`
-2. **Add descriptions** - Explain the purpose and schedule
-3. **Handle errors** - Use try_catch for external dependencies
-4. **Log important events** - Use debug.log for tracking
-5. **Use appropriate frequency** - Don't run more often than needed
-6. **Consider timezone** - Schedule uses UTC (+0000)
-7. **Batch operations** - Process in chunks for large datasets
-8. **Set end dates** - Use ends_on for temporary schedules
+1. **Descriptive names** - Indicate what and when: `daily_cleanup`, `hourly_sync`
+2. **Handle errors** - Use try_catch for external dependencies
+3. **Consider timezone** - Schedule uses UTC (+0000)
+4. **Batch operations** - Process in chunks for large datasets
+5. **Set end dates** - Use ends_on for temporary schedules

package/xanoscript_docs/testing.md

@@ -325,11 +325,8 @@ function "calculate_discount" {
 
 ## Best Practices
 
-1. **Test happy paths** - Verify expected behavior works
-2. **Test edge cases** - Empty arrays, null values, boundaries
-3. **Test error cases** - Invalid inputs, missing data
-4. **Use mocks** - Isolate from external dependencies
-5. **Descriptive test names** - Explain what's being tested
-6. **One assertion focus** - Each test verifies one behavior
-7. **Keep tests independent** - No shared state between tests
-8. **Test at boundaries** - Min/max values, length limits
+1. **Test happy paths, edge cases, and errors** - Cover expected, boundary, and failure scenarios
+2. **Use mocks** - Isolate from external dependencies
+3. **Descriptive test names** - Explain what's being tested
+4. **One assertion focus** - Each test verifies one behavior
+5. **Keep tests independent** - No shared state between tests

package/xanoscript_docs/tools.md

@@ -62,20 +62,15 @@ tool "get_user_by_email" {
 
 ## Input Block
 
-Same as functions, but descriptions are especially important:
+For complete type reference, use `xanoscript_docs({ keyword: "input" })`. For tools, input `description` fields are sent to the AI, so write them clearly:
 
 ```xs
 input {
-  int order_id {
-    description = "The unique order ID to look up"
-  }
+  int order_id { description = "The unique order ID to look up" }
   enum status {
     description = "New status to set"
     values = ["pending", "processing", "shipped", "delivered"]
   }
-  text reason? {
-    description = "Optional reason for the status change"
-  }
 }
 ```
 
@@ -299,7 +294,4 @@ tool "cancel_order" {
 2. **Describe all inputs** - Help AI construct valid requests
 3. **Use enums for fixed options** - Reduces AI errors
 4. **Keep tools focused** - One task per tool
-5. **Handle errors gracefully** - Return clear error messages
-6. **Validate inputs** - Use filters and preconditions
-7. **Limit response size** - Don't return huge datasets
-8. **Use composition** - Call other tools for complex operations
+5. **Limit response size** - Don't return huge datasets