propose_pipeline_schema
Preview a tested tap's rows and recommend a destination column type for each column before the pipeline exists, so you can confirm the schema and pass it to create_pipeline.
Instructions
Preview a tested tap's rows and recommend a destination column type for each column, BEFORE the pipeline exists. Uses the rows from the tap's last successful test (nothing is pushed) and runs the tap again only when none are held or a higher limit asks for more, then infers a type per column from the rows the tap actually produced. Recommendations are conservative: a column is typed only on strong evidence; otherwise it stays string with a visible reason — stringReason when a value blocked a type, note when too few non-null values were present (all-null or a thin sample). Call it after test_tap succeeds and before create_pipeline. Present the returned fields to the user as a table (column, recommended type, evidence) and ask them to confirm or change the types, or to pull more rows (call again with a higher limit). Then pass the confirmed list as schema_fields on create_pipeline — no sample content needed — and attach the tap with update_tap (target_pipeline). A failed test comes back verbatim (fix the tap first). Vector destinations (pgvector, qdrant, weaviate, milvus, chroma) and mongodb return typeGrid: false with a preview only — they have no column schema — for a vector destination go straight to create_pipeline with name and destination only; no checks, transformations or protection question (MongoDB stores documents as-is; create it with a few preview rows as a JSON content_text sample, filename ending in .json, never schema_fields). An older Datris server answers with a "server too old" error; then fall back to content_text on create_pipeline. Only a result whose status is schema_proposal is a proposal; anything else (a failed test, no rows, an error) means no schema and no table were shown to the user, so tell the user what failed in one or two plain sentences with the tool's stated next step, and do not ask the types question, do not call ask_user about types and do not mention a table. If this Datris instance's agent policy requires a person to approve this action, the call does NOT perform it: it returns status pending_approval with an approvalId. Tell the user it is waiting for approval in Datris, then poll get_approval with that id (pause with wait_seconds between polls) — do not re-issue the action.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"tap": "<tap>",
"destination": "<destination>"
},
"name": "propose_pipeline_schema"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tap | Yes | Name of the tap whose rows define the schema (create and test it first) | |
| limit | No | Rows to preview and infer from (default 20). Raise it when the user wants more evidence. | |
| reason | No | Optional one-line reason for this change, recorded in the platform's audit log and shown to anyone asked to approve it. | |
| destination | Yes | The destination the pipeline will use. Vector destinations and mongodb get a preview only (no type grid). |