qingflow-mcp 0.3.14 → 0.3.16
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 +7 -1
- package/dist/server.js +806 -485
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -207,7 +207,13 @@ Deterministic read protocol (list/summary/aggregate):
|
|
|
207
207
|
4. `strict_full=true` makes incomplete results fail fast with `NEED_MORE_DATA`.
|
|
208
208
|
- 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
209
|
5. Error payloads expose `error_code` and `fix_hint` for actionable retries.
|
|
210
|
-
6.
|
|
210
|
+
6. Public MCP `inputSchema` is strict:
|
|
211
|
+
- numbers must be native JSON numbers
|
|
212
|
+
- arrays must be native JSON arrays
|
|
213
|
+
- objects must be native JSON objects
|
|
214
|
+
- booleans must be native JSON booleans
|
|
215
|
+
- unknown fields are rejected by the MCP boundary
|
|
216
|
+
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
217
|
|
|
212
218
|
For `qf_query(summary)` and `qf_records_aggregate`, read `data.summary.completeness` / `data.completeness` before concluding:
|
|
213
219
|
|