plan_cold_plate¶
Plan liquid cold-plate designs that cool a GPU or IGBT within its temperature and pressure-drop limits.
Scope: geometry:write. Catalogue annotation: Read. Additional ownership and role checks may apply.
REST: POST /v1/design/cold-plates/plan.
Arguments¶
Field |
Type / accepted values |
Required |
Default |
Constraints / meaning |
|---|---|---|---|---|
|
string (uuid) |
Yes |
Omitted |
|
|
string (uuid) |
Yes |
Omitted |
|
|
map of JsonValue |
No |
Omitted |
|
|
map of array of JsonValue |
No |
Omitted |
Explicit grid of up to 16 candidates; use evaluated best parameters as the next baseline |
Calling the tool¶
Use tools/call with this tool’s exact name and an arguments object matching the fields above. Get the complete live schema before supplying advanced controls:
{
"name": "get_tool_schema",
"arguments": {
"name": "plan_cold_plate",
"include_definitions": false
}
}
Result and continuation¶
Inspect isError and structuredContent. Keep returned job, operation and artifact IDs. A pending operation_id is followed with get_operation; a compute job is followed with get_job. A wait timeout does not cancel work. Follow returned polling intervals and retain the same idempotency key when reconciling the same submission.
See agent workflow, jobs and operations, uploads, results and error recovery for the applicable lifecycle. MCP annotations describe tool behaviour; they are not blanket permission to run paid work or change account state.