mcp-zenskar 1.0.2 → 1.0.3

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.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/src/mcp-config.json +1 -1
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "mcp-zenskar",
3
- "version": "1.0.2",
3
+ "version": "1.0.3",
4
4
  "description": "Model Context Protocol (MCP) server for Zenskar API - customer management, invoicing, and billing operations",
5
5
  "type": "module",
6
6
  "main": "src/server.js",
package/src/mcp-config.json CHANGED
@@ -4037,7 +4037,7 @@
4037
4037
  },
4038
4038
  {
4039
4039
  "name": "dataschema",
4040
- "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\"}",
4040
+ "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\"}",
4041
4041
  "type": "object",
4042
4042
  "required": true,
4043
4043
  "position": "body"