qingflow-mcp 0.3.14 → 0.4.0
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 +9 -2
- package/dist/server.js +2154 -407
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -108,7 +108,7 @@ npm i -g git+https://github.com/853046310/qingflow-mcp.git
|
|
|
108
108
|
Install from npm (pinned version):
|
|
109
109
|
|
|
110
110
|
```bash
|
|
111
|
-
npm i -g qingflow-mcp@0.
|
|
111
|
+
npm i -g qingflow-mcp@0.4.0
|
|
112
112
|
```
|
|
113
113
|
|
|
114
114
|
Or one-click installer:
|
|
@@ -151,6 +151,7 @@ MCP client config example:
|
|
|
151
151
|
Full calling contract (Chinese):
|
|
152
152
|
|
|
153
153
|
- [MCP 调用规范](./docs/MCP_CALLING_SPEC.md)
|
|
154
|
+
- [vNext Agent-Native 设计稿](./docs/VNEXT_AGENT_NATIVE_DESIGN.md)
|
|
154
155
|
|
|
155
156
|
## Unified Query (`qf_query`)
|
|
156
157
|
|
|
@@ -207,7 +208,13 @@ Deterministic read protocol (list/summary/aggregate):
|
|
|
207
208
|
4. `strict_full=true` makes incomplete results fail fast with `NEED_MORE_DATA`.
|
|
208
209
|
- for `qf_query(summary)`, `strict_full` enforces raw source scan completeness; sample rows may still be capped by `max_rows`, which is reflected by `output_page_complete=false`
|
|
209
210
|
5. Error payloads expose `error_code` and `fix_hint` for actionable retries.
|
|
210
|
-
6.
|
|
211
|
+
6. Public MCP `inputSchema` is strict:
|
|
212
|
+
- numbers must be native JSON numbers
|
|
213
|
+
- arrays must be native JSON arrays
|
|
214
|
+
- objects must be native JSON objects
|
|
215
|
+
- booleans must be native JSON booleans
|
|
216
|
+
- unknown fields are rejected by the MCP boundary
|
|
217
|
+
7. Use `qf_query_plan` as the only preflight tool when the agent is unsure about arguments. It can normalize loose/model-shaped inputs before a real query is issued.
|
|
211
218
|
|
|
212
219
|
For `qf_query(summary)` and `qf_records_aggregate`, read `data.summary.completeness` / `data.completeness` before concluding:
|
|
213
220
|
|