Gradient Dynamics: thermal and CFD simulation

View mesh cross-section

view_mesh_section

Read-onlyIdempotent

Show a 2D cross-section of actual volume-cell edges cut from a completed or verified awaiting_decision mesh_cgns artifact. Use this for requested mesh cross-sections, not geometry clipping. Sections and PNGs supplement view_mesh; they do not replace its interactive 3D browser viewer unless the user explicitly requests 2D only. Set axis and position_m in the saved mesh coordinate frame; optionally select an exact zone or crop. Returns an interactive 2D pan/zoom browser viewer, a supplementary PNG picture and saved PNG/HTML artifacts; no mesh regeneration. Y is vertical in X/Z sections. Supports structured and unstructured CGNS with NGON/NFACE or linear tetra/prism/pyramid/hexa topology, up to 1 GiB input and 200,000 section edges; no silent decimation. Open viewer_url in a browser and show its labelled link; include the PNG when requested. For a combined surface/section workspace use assemble_mesh_viewer with the returned JSON artifact_id. Surface clipping is not a substitute. Keep infrastructure details out of the answer. Repeating the same request reuses its saved section. 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": {
      "position_m": "<position_m>",
      "artifact_id": "<artifact_id>"
    },
    "name": "view_mesh_section"
  }
}

Input Schema

Name	Required	Description	Default
`axis`	No		z
`zone`	No	Optional exact mesh zone from its summary; omit for all zones.
`position_m`	Yes	Plane coordinate in metres in the saved mesh frame, e.g. z=0.093 m.
`artifact_id`	Yes
`view_bounds_m`	No	Optional crop [horizontal_min, vertical_min, horizontal_max, vertical_max], metres. X/Y for a Z section, Z/Y for X, X/Z for Y.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world, so the description creditably goes further: no mesh regeneration, no silent decimation, 1 GiB input and 200,000 edge limits, supported CGNS topologies, cached results for repeated requests, and a documented async path that may return a pending operation_id to poll with retry_after_seconds. Deductions only because 'verify' semantics of awaiting_decision artifacts are referenced but not explained and the pending-operation behavior lacks an indication of typical latency or failure modes.

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?

Front-loaded with the operation, then constraints, then output and continuation — a sound ordering. It is dense and a few sentences overlap ('not geometry clipping' vs 'Surface clipping is not a substitute'), and 'Keep infrastructure details out of the answer' is an answer-styling instruction rather than tool semantics, but overall little is wasted.

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 read-only viewer with an output schema, a rich parameter set, and an async fallback, this covers essentially everything an agent needs: scope, limits, output surfaces (viewer_url, PNG, HTML artifacts), artifact_id handoff to assemble_mesh_viewer, and the polling protocol. No material gap remains.

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?

Schema coverage is 60%, so the description must compensate, and it does where it matters most: it pins axis and position_m to the saved mesh coordinate frame and adds the orientation rule 'Y is vertical in X/Z sections', which the schema does not state. Zone and crop are only gestured at ('optionally select an exact zone or crop'), leaving the details to the field descriptions.

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 — 'Show a 2D cross-section of actual volume-cell edges cut from a completed or verified awaiting_decision mesh_cgns artifact' — and immediately fences off the confusable operations ('not geometry clipping', surface clipping not a substitute). An agent can distinguish it from view_mesh and view_geometry without opening any schema.

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?

Explicit about when to use it (requested mesh cross-sections), when not to (geometry clipping, surface clipping as a substitute), and how it relates to named alternatives: it supplements view_mesh rather than replacing the 3D browser unless the user asks for 2D only, and assemble_mesh_viewer is the route for a combined workspace. The get_operation continuation path is spelled out too.

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?