Gradient Dynamics: thermal and CFD simulation

Check geometry with the mesher

check_geometry

Read-onlyIdempotent

Check an owned STL or STEP with the native octree mesher before meshing: open and non-manifold edges, self-intersections, separate bodies, zero-area triangles and the part's size in metres against its declared units, each issue with its fix. A STEP with several solids also lists the mesher's names for them (the CAD labels in lower case), which per-part controls use; a CHT mesh's expected_region_names are the labels as written in the CAD. This works where inspect_mesh_geometry cannot read STEP. meshable=false means the mesher cannot mesh it as given. Warnings still mesh: the mesher closes small holes or shrink-wraps a dirty surface, which rounds sharp edges; tell the user before meshing such a surface. No mesh is built and nothing is charged. 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": "check_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.8/5.0

Behavior5/5

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

Beyond the readOnly and non-destructive annotations, it states that no mesh is built and nothing is charged, explains that meshable=false blocks meshing, and notes that warnings still mesh because the mesher may close holes or shrink-wrap dirty surfaces and round sharp edges. It also discloses the asynchronous pending-operation behavior and the required polling workflow.

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?

The purpose is front-loaded and the dense paragraph contains little waste for a workflow with many important caveats. However, the pending-operation instructions and warning behavior are packed into one long paragraph rather than separated into clearer structural units.

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?

For a geometry-validation tool with one input parameter, an output schema, and rich annotations, the description covers purpose, defect types, alternatives, warning semantics, charging behavior, and async continuation. It leaves return-value fields to the output schema while providing the operational context an agent needs.

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?

The schema only defines artifact_id as a UUID with no description, but the description adds that the artifact must be an owned STL or STEP to be checked. It does not explain how to obtain the artifact_id or add UUID-level details, but it meaningfully scopes the single parameter beyond the raw 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?

The description uses a specific verb and resource: it checks an owned STL or STEP with the native octree mesher before meshing. It enumerates the defect classes and unit-size checks, and explicitly distinguishes itself from inspect_mesh_geometry by noting it works where inspect_mesh_geometry cannot read 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?

It clearly states the pre-meshing context and names the alternative condition: use this where inspect_mesh_geometry cannot read STEP. It also explains how to proceed when a pending operation_id is returned via get_operation and warns not to resubmit to check progress.

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?