Gradient Dynamics: thermal and CFD simulation

Prepare job viewer

prepare_job_viewer

Idempotent

Prepare or reopen a finished geometry, verified mesh candidate or published simulation result in its default interactive 3D browser viewer with orbit/pan/zoom. get_job normally does this automatically; PNG snapshots and 2D sections do not replace this view. Uses only this job’s saved outputs and one durable cached preparation; it never reruns compute, creates extra sections or retries failed/cancelled preparation. Show viewer_url automatically in a labelled browser link, preserving the complete fragment. Pending viewer.operation_id or operation_id is continued with get_operation. Report visualization failure separately from job outcome. Requires jobs:read and artifacts:read.

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": {
      "job_id": "<job_id>"
    },
    "name": "prepare_job_viewer"
  }
}

Input Schema

Name	Required	Description	Default
`job_id`	Yes

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

Behavior5/5

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

Goes well past the annotations: it discloses no recompute, reuse of one durable cached preparation, no extra sections, no retry of failed/cancelled preparation, the required scopes jobs:read and artifacts:read, and that visualization failure should be reported separately from job outcome. readOnlyHint=false is consistent with a preparation that persists a viewer artifact, so there is no contradiction.

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 core purpose, then constraints, then operational handling — every sentence carries information. It is slightly dense and mixes agent-side presentation instructions ('Show viewer_url automatically in a labelled browser link, preserving the complete fragment') into a behavior description, but 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?

An output schema exists so return-value explanation is unnecessary, and the description still covers auth requirements, caching limits, failure separation, and operation continuation. Nothing material is missing for a single-parameter preparation tool.

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 coverage is 0% and the only parameter, job_id, is never described explicitly; the description only implies it selects 'this job’s saved outputs.' For a UUID job identifier that is largely self-evident from the schema's uuid format, so this is adequate but adds no real meaning.

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 set: 'Prepare or reopen a finished geometry, verified mesh candidate or published simulation result in its default interactive 3D browser viewer with orbit/pan/zoom.' It also scopes what it is not (PNG snapshots, 2D sections) so an agent can separate it from the other prepare_* tools.

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 an explicit alternative ('get_job normally does this automatically'), explicit non-substitutes ('PNG snapshots and 2D sections do not replace this view'), and a routing rule for pending work ('Pending viewer.operation_id or operation_id is continued with get_operation'). An agent knows both when to call this and what to do instead in adjacent cases.

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?