mcp-zenskar 1.0.2 → 1.0.4

package/README.md

@@ -125,5 +125,5 @@ MIT
 ## Support
 
 For issues and support:
-- GitHub Issues: https://github.com/your-org/mcp-zenskar/issues
+- GitHub Issues: https://github.com/zenskar/mcp-zenskar/issues
 - Zenskar Documentation: https://docs.zenskar.com

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mcp-zenskar",
-  "version": "1.0.2",
+  "version": "1.0.4",
   "description": "Model Context Protocol (MCP) server for Zenskar API - customer management, invoicing, and billing operations",
   "type": "module",
   "main": "src/server.js",

package/src/mcp-config.json

@@ -4037,7 +4037,7 @@
         },
         {
           "name": "dataschema",
-          "description": "Data schema of raw metric (JSON object). Must include 'timestamp' and 'customer_id' fields. Supported data types: Bool, UUID, Int64, Date32, String, Decimal, Float64, DateTime64. Example: {\"data\": {\"field1\": \"String\", \"field2\": \"Int64\"}, \"timestamp\": \"DateTime64\", \"customer_id\": \"String\"}",
+          "description": "Data schema of raw metric (JSON object). Structure: {\"data\": {custom_fields}, \"timestamp\": \"DateTime64\", \"customer_id\": \"String\"}. The 'data' object contains your custom fields, while 'timestamp' and 'customer_id' are separate required fields. Supported data types: Bool, UUID, Int64, Date32, String, Decimal, Float64, DateTime64. Example: {\"data\": {\"usage_amount\": \"Decimal\", \"feature_id\": \"UUID\"}, \"timestamp\": \"DateTime64\", \"customer_id\": \"String\"}",
           "type": "object",
           "required": true,
           "position": "body"