Gradient Dynamics: thermal and CFD simulation

Reconstruct editable CAD

reconstruct_cad

Idempotent

Create a durable parametric reconstruction of an owned STEP or 3MF artifact, measured against the uploaded geometry. With your own key this runs native_features mode: deterministic measured features and parameter controls, without model composition. Hosted composition, which uses Gradient Dynamics' own design model with the brief and context_artifact_ids, is available to Design and Studio sessions only; a key requesting it is refused. Retains source bodies; 3MF surfaces remain tessellated and fitted parameters carry explicit fidelity/edit-range limits. An exact original feature history is not implied. Returns an operation ID: poll get_operation for stages, then inspect fidelity, source_format, fitted versus retained features, edit ranges, input_groups and verified per-parameter scope. Groups organize controls without coupling them; composition provenance identifies the authored plan. No mesh or simulation starts. Never replace imported CAD with an approximate template.

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": {
      "artifact_id": "<artifact_id>"
    },
    "name": "reconstruct_cad"
  }
}

Input Schema

Name	Required	Description	Default
`brief`	No
`parameters`	No
`artifact_id`	Yes
`tolerance_mm`	No
`composition_mode`	No		hosted
`context_artifact_ids`	No	Owned project design-source artifacts containing supplier/manufacturing text, heat maps or reference images. Raw CAD is not sent to the hosted model.
`expected_parent_sha256`	No
`parent_reconstruction_id`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.3/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well beyond the annotations: discloses tier-gated authorization and refusal behavior, that source bodies are retained, that 3MF surfaces stay tessellated and fitted parameters carry fidelity/edit-range limits, that exact original feature history is not implied, and that 'no mesh or simulation starts.' Those are material expectations an agent could not infer from readOnlyHint/openWorldHint/idempotentHint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded and the workflow (returns an operation ID, poll get_operation, then inspect) follows in a logical order. It is dense with clause-stacked sentences, and the closing imperative 'Never replace imported CAD with an approximate template' reads as guidance padding rather than tool definition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex, tier-gated, asynchronous operation it covers the mode distinction, fidelity caveats, return workflow, and what does not happen downstream; an output schema exists so return values need not be spelled out. The gap is the lineage parameters (parent_reconstruction_id, expected_parent_sha256) and tolerance, whose role in re-reconstruction is unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 13% across 8 parameters, so the description carries real burden. It usefully explains composition_mode and that hosted mode consumes brief and context_artifact_ids, but tolerance_mm, parameters, parent_reconstruction_id, and expected_parent_sha256 are never given meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb and resource: 'Create a durable parametric reconstruction of an owned STEP or 3MF artifact, measured against the uploaded geometry.' Scope (owed artifacts, STEP/3MF only) and the mode split are stated, which separates it from edit_reconstructed_cad and get_cad_reconstruction without needing their schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states which accounts can use hosted composition ('Design and Studio sessions only; a key requesting it is refused') versus native_features 'with your own key', which is real when-to-use routing. It also warns against substituting an approximate template. It does not name the follow-up/alternative siblings (edit_reconstructed_cad, get_cad_reconstruction) directly, keeping it at 4.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Gradient Dynamics: thermal and CFD simulation tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?