Gradient Dynamics: thermal and CFD simulation

Upload reference document

open_design_source_upload

Fallback file picker for a new supplier PDF, requirements TXT, CSV heat map/table or PNG/JPEG when the chat host cannot hand off its attachment. Prefer import_design_source_attachment for a host-provided file reference, or reuse a known ready artifact. API handles transfer and SHA-256; no shell or signed-URL upload needed. Show the picker or Upload source link once; retain artifact ID and continue when ready. Images are visual evidence, not measured dimensions or numeric heat maps. Server cannot read client file paths.

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": {
      "project_id": "<project_id>",
      "filename": "<filename>",
      "media_type": "<media_type>"
    },
    "name": "open_design_source_upload"
  }
}

Input Schema

Name	Required	Description	Default
`sha256`	No
`filename`	Yes
`media_type`	Yes
`project_id`	Yes
`size_bytes`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations only declare the generic write/open-world profile; the description adds what actually matters here: the API handles transfer and SHA-256, no shell or signed-URL upload is required, the artifact ID must be retained to continue, and the server cannot read client file paths. It also clarifies that images count as visual evidence rather than measured dimensions or numeric heat maps, which is a real interpretation constraint beyond annotations.

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 fallback role and tightly packed with useful routing and operand facts; nearly every sentence earns its place. Slightly dense and run-on, with the operational instruction ('Show the picker... once') buried mid-paragraph rather than at the end or start.

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?

An output schema exists, so return values need not be explained, and the description covers routing, transfer mechanics, client-path limits, and post-call continuation. It omits whether an upload replaces or coexists with an existing design source, which matters for a non-idempotent write tool.

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

Parameters2/5

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

Schema description coverage is 0% across five parameters, so the description carries the burden, and it only partially does. It enumerates the media types implicitly (PDF, TXT, CSV, PNG/JPEG) and references SHA-256 handling, but never explains filename, size_bytes (including the 10 MB cap), or project_id, leaving the agent to infer their meaning from the schema alone.

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+resource (a fallback file picker for a supplier PDF, requirements TXT, CSV heat map/table, or PNG/JPEG) and names the exact conditions under which it applies. It explicitly separates itself from import_design_source_attachment, so an agent can route between them without opening a 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?

Gives explicit when-to-use ('when the chat host cannot hand off its attachment'), names the preferred alternative (import_design_source_attachment for a host-provided file reference), and offers a third path (reuse a known ready artifact). It also says to show the picker once, which prevents repeated invocation.

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?