@zltquant/zlt-mcp 0.6.0-beta.1 → 0.6.0-beta.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zltquant/zlt-mcp",
-  "version": "0.6.0-beta.1",
+  "version": "0.6.0-beta.2",
   "description": "智量通 ZLT Quant MCP server（Windows x64；量化策略创建与本地回测）",
   "bin": {
     "zlt-mcp": "./zlt-mcp-proxy.bundle.cjs"

package/zlt-mcp-proxy.bundle.cjs

@@ -27714,6 +27714,8 @@ if (process.argv.length <= 2) {
 Input: omitted arguments mean {}; use --args-json for small objects and --args-file
 for nested configuration or shell-sensitive text. Follow the selected tool schema
 from list --tool <name> --json. Windows paths must be native paths (C:/...), not /c/....
+Tool schema properties are JSON keys, NOT CLI flags: use --args-json '{"params": [...]}'
+for a tool's params property, not --params. Pass the complete argument object.
 Output: by default stdout contains the complete MCP JSON envelope plus cliProvenance.
 JSON business responses are inside content[].text (or structuredContent when present).
 Use --output-json for large results or downstream evidence: it saves the complete
@@ -27795,7 +27797,12 @@ Credentials belong in the configured local credential store, never in arguments.
       if (options.tool !== void 0) {
         const tools2 = Array.isArray(result.tools) ? result.tools.filter((tool) => tool.name === options.tool) : [];
         if (tools2.length === 0) throw new Error(`Unknown tool: ${options.tool}. Use list to discover available names.`);
-        result = { ...result, tools: tools2 };
+        result = { ...result, tools: tools2, cliUsage: {
+          command: `call ${options.tool}`,
+          argumentsOption: "--args-json",
+          argumentsAreCliFlags: false,
+          instruction: "Put tool schema properties inside one JSON object passed to --args-json (or use --args-file). Do not turn properties into --flags."
+        } };
       }
       if (options.json) {
         process.stdout.write(JSON.stringify(withCliProvenance(result)) + "\n");