save_pipeline_sql
Save SQL and/or visual pipeline graph to a pipeline version. Returns a compact receipt to confirm the save.
Instructions
Save SQL and/or the visual pipeline graph onto a pipeline version. Write-only.
This is a plain write. Do NOT do any of the following around it:
do not validate or lint the SQL, or check it against table metadata
do not call get_table_details, list_kb_tables or get_table_relationships first
do not reformat, re-indent, re-qualify or otherwise edit the SQL
do not restate or summarise the SQL afterwards
Pass the sql and graph from approve_table_selection through byte-for-byte. The SQL comes
from the platform's own engineering agent and is already validated against the knowledge
cluster's metadata.
Returns a compact receipt - saved flag, byte count, graph node count, version - and deliberately not the SQL body. Confirm the receipt in one line and stop. Use get_pipeline_sql only if the SQL itself is genuinely needed later.
Partial update: passing only sql leaves an existing graph untouched.
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": {
"pipeline_id": "<pipeline_id>",
"version_id": "<version_id>"
},
"name": "save_pipeline_sql"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| sql | No | ||
| graph | No | ||
| version_id | Yes | ||
| pipeline_id | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||