snow-flow 3.1.0 → 3.1.1

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.
package/README.md CHANGED
@@ -100,28 +100,36 @@ snow-flow auth login
100
100
  The revolutionary `snow_query_table` replaces all table-specific query tools with intelligent performance optimization:
101
101
 
102
102
  ```javascript
103
- // Smart Performance Modes - LLM chooses the best approach:
103
+ // Smart Performance Modes - System auto-detects the best approach:
104
104
 
105
- // 1. Count-only (default) - 99.9% memory savings for ML training
106
- snow_query_table({ table: "incident", query: "state!=7", limit: 2000 })
107
- // Returns: {total_results: 2000} - Only 13 bytes!
105
+ // 1. Analytics mode - OMIT limit for ALL records with minimal fields
106
+ snow_query_table({
107
+ table: "incident",
108
+ query: "state!=7",
109
+ fields: ["sys_created_on", "priority"] // Get ALL records, minimal data
110
+ })
111
+ // Auto-detects analytics context and returns ALL records!
108
112
 
109
- // 2. Specific fields - Get exactly what you need
113
+ // 2. Count-only mode - Ultra efficient for large datasets
110
114
  snow_query_table({
111
115
  table: "sc_request",
112
- fields: ["number", "short_description", "requested_for"],
113
- include_display_values: true // Names instead of sys_ids
116
+ include_content: false // Just counts, no data
114
117
  })
118
+ // Returns: {total_results: 15234} - Maximum efficiency!
115
119
 
116
- // 3. Group by aggregation - Analytics and statistics
120
+ // 3. Display mode - Limited records with full details
117
121
  snow_query_table({
118
122
  table: "problem",
119
- group_by: "category",
120
- order_by: "-priority" // - means descending (highest first)
123
+ limit: 50, // Explicitly limit for display
124
+ include_display_values: true
121
125
  })
122
126
 
123
- // 4. Full content - When complete data is needed
124
- snow_query_table({ table: "change_request", include_content: true })
127
+ // 4. Group by aggregation - Server-side analytics
128
+ snow_query_table({
129
+ table: "change_request",
130
+ group_by: "risk",
131
+ order_by: "-count" // Sorted by frequency
132
+ })
125
133
  ```
126
134
 
127
135
  Works with ANY table: `incident`, `sc_request`, `problem`, `cmdb_ci`, even `u_custom_table`!
@@ -872,7 +872,7 @@ class ServiceNowOperationsMCP {
872
872
  // Apply intelligent limit strategy
873
873
  const limit = determineSmartLimit(args.limit, table, query, include_content || !!fields, fields);
874
874
  // For analytics, we want NO limit at all
875
- const effectiveLimit = limit === undefined ? 999999 : limit; // ServiceNow max is usually 10000 per call
875
+ const effectiveLimit = limit === undefined ? 999999 : limit; // ServiceNow theoretical max (actual varies by instance)
876
876
  // 🚨 ML Training Warning for low limits
877
877
  const isMLTrainingContext = query?.toLowerCase().includes('train') ||
878
878
  query?.toLowerCase().includes('ml') ||
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "snow-flow",
3
- "version": "3.1.0",
3
+ "version": "3.1.1",
4
4
  "description": "Snow-Flow v3.0.18: DIRECT API VERIFICATION! 🚀 Replaced unreliable searchRecords with direct API calls (snow_query_table style) for widget verification. All null/403 error recovery now uses GET /api/now/table/sp_widget with precise queries. NO MORE FALSE NEGATIVES - verification works consistently every time!",
5
5
  "main": "dist/index.js",
6
6
  "type": "commonjs",