Create your first implicit body¶
This example creates a cylinder with a radius of 12 mm and a height of 30 mm. It introduces an editable document and durable geometry artifacts without starting a mesh or simulation.
1. Discover the operation¶
Through MCP, call get_design_operation_schema, then call_design_operation with name="catalogue". Check the inputs for primitive.cylinder. REST clients use the design operation routes.
2. Define the document¶
{
"schema_version": "gd.design/v1",
"id": "first-cylinder",
"name": "First cylinder",
"units": "mm",
"revision": 0,
"nodes": [
{
"id": "body",
"op": "primitive.cylinder",
"inputs": {"radius": 12, "height": 30}
}
],
"outputs": {"solid": {"ref": "body"}}
}
Send this document as the body of the design operation validate. Read the returned validation result before evaluating or exporting it. The explicit output name solid identifies the intended physical body; use meaningful names for real assemblies.
3. Create durable geometry¶
Send POST /v1/geometry/validate a request containing the document above under document, plus outputs: ["stl", "design"]. Once valid, submit the same request to POST /v1/geometries with an idempotency key. MCP equivalents are validate_geometry and create_geometry.
Poll the returned job ID. On completion, retain the design artifact and surface artifact IDs and open the saved viewer. Check the expected dimensions: 24 mm across and 30 mm high. A preview should match the intended orientation and scale.
4. Make an engineering change¶
Change the radius to 15 mm, validate the candidate, and compare its bounds with the original. Save the new design with a new intended submission key. For shared Studio work, use authoring drafts so the engineer can review the change before it becomes a project revision.
Continue with parameters, named simulation regions, or meshing. This body alone does not define a complete fluid domain or boundary-condition set.