Gradient Dynamics: thermal and CFD simulation

View geometry

view_geometry

Read-onlyIdempotent

Default for visualizing geometry: open a solid interactive 3D view in the Gradient Dynamics browser viewer for a generated geometry_surface or verified uploaded surface STL, including imported CAD surfaces. A static picture or 2D section alone does not replace this viewer unless explicitly requested. Uploaded STL needs no geometry job or second upload. Large ASCII uploads receive a bounded binary display derivative with every triangle retained; keep source_artifact_id for inspection and meshing. Render Y-up with orbit/pan/zoom, fit, standard views, sections, measurements and PNG capture. Measurements use tessellation, not exact CAD. Open viewer_url in the browser, not an embedded chat panel; show one labelled browser link if opening is unavailable. Continue already requested meshing/mesh sections. No geometry regeneration. Raw STEP is not rendered directly by this STL viewer. May return a pending operation_id instead of the finished result. Continue with get_operation at retry_after_seconds intervals; on success use result, then continue the requested workflow. Do not resubmit to check progress.

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": "view_geometry"
  }
}

Input Schema

Name	Required	Description	Default
`artifact_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial context beyond them: asynchronous pending operation_id with get_operation polling at retry_after_seconds, an explicit 'Do not resubmit to check progress' rule, unbounded-vs-binary handling of large ASCII uploads, and the caveat that measurements use tessellation rather than exact CAD.

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

Conciseness3/5

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

Information-dense and front-loaded with the primary purpose first, but the body is a long run-on sequence of imperatives and caveats (viewer_url handling, polling, tessellation, ASCII derivatives) with no grouping, making it harder to scan than necessary.

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

Completeness5/5

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

Given an output schema and rich annotations, everything an agent needs is present: what to open, how to present the link, how to handle the async pending state and polling interval, and what not to do (resubmit, regenerate geometry, treat tessellated measurements as exact).

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

Parameters4/5

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

Only one required parameter with 0% schema coverage, so the description carries the burden. It implies the parameter is the surface artifact via 'generated geometry_surface or verified uploaded surface STL' and 'keep source_artifact_id for inspection and meshing', but never explicitly maps artifact_id to those concepts or states accepted artifact kinds.

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?

States a specific verb and resource: opens an interactive 3D view in the Gradient Dynamics browser viewer for a generated geometry_surface or verified uploaded surface STL. It also names what it is not (mesh sections, convergence history, simulation results) by constraining scope to geometry and explicitly excluding raw STEP.

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

Usage Guidelines5/5

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

Gives explicit when-to-use ('Default for visualizing geometry'), when-not ('A static picture or 2D section alone does not replace this viewer unless explicitly requested'), and boundaries against siblings ('Continue already requested meshing/mesh sections', 'No geometry regeneration'). Also states 'Raw STEP is not rendered directly by this STL viewer', routing the agent away when the input type is wrong.

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?