Skip to main content
Glama

cad_render

Read-onlyIdempotent

Render the active CAD document to PNG, GIF, or WebGL delta using orthographic, 3D view, section, exploded, or animation modes. Pick the mode that produces the visual you need.

Instructions

Render the document in a selected mode.

按 ``mode`` 渲染当前文档:
- ortho:2D 正交投影 PNG(top/front/side)
- view_3d:按存储的三维视图定义渲染 PNG
- section:平面剖切 PNG(plane=XY/YZ/XZ)
- explode:爆炸视图 PNG
- animation:orbit/turntable GIF 动画
- webgl:WebGL 增量同步 delta

When not to use: ``cad_render`` produces images / sync deltas only. To
store or edit a named view *definition* before rendering use
``cad_view``; for drawing-sheet exports (SVG/DXF/PDF) use
``cad_drawing`` (action=export); for interop geometry files use
``cad_file`` (export).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
renderYesRender request, discriminated by `mode`: ortho, view_3d, section, explode, animation or webgl.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeYesRender mode used
pathNoPath of the written output file
statusYesOperation status
messageNoStatus description
payloadNoExtra mode-specific data (webgl deltas)
data_uriNoOutput data URI (base64)
size_bytesNoOutput size in bytes
Behavior4/5

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

Annotations already declare read-only, idempotent, and non-destructive hints. The description adds valuable context that it 'produces images / sync deltas only' and details output formats per mode, reinforcing the non-mutating behavior. It does not contradict annotations and provides useful output-format context.

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 description is front-loaded with a one-line summary, followed by a concise mode list and a well-structured 'When not to use' section. The bilingual list adds a bit of redundancy but remains compact and every line carries informational value.

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 complex tool with six discriminated modes, the description covers all relevant scenarios: what it does, which modes exist, what output each produces, and clearly explains when to use sibling tools instead. The output schema is present, so return-value details are already handled, making the description adequate for safe tool selection.

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 100% and each parameter has its own description. The description adds a mode-to-output-format mapping (e.g., ortho -> PNG, animation -> GIF, webgl -> delta) that the schema does not capture, helping the agent understand the semantic difference between modes beyond their 'const' values.

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 clearly states the tool renders the document in a selected mode and enumerates six modes with their output types (PNG, GIF, sync delta). It distinguishes itself from sibling tools by explicitly naming cad_view, cad_drawing, and cad_file as alternatives for other operations.

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?

Provides explicit 'When not to use' guidance with direct references to cad_view (storing/editing view definitions), cad_drawing (SVG/DXF/PDF exports), and cad_file (interop geometry files). This clearly directs the agent to the right tool for adjacent tasks.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Tianshang301/TianshangCAD'

If you have feedback or need assistance with the MCP directory API, please join our Discord server