Skip to main content
Glama

Render View

render_view
Read-only

Render shaped objects as PNG images from isometric or orthographic views for geometry inspection, with optional triangle edges.

Instructions

Render an isometric/orthographic view of a shaped object as a PNG.

view: 'iso' | 'top' | 'bottom' | 'front' | 'back' | 'left' | 'right' | 'side'. deflection: tessellation accuracy in mm (smaller = finer mesh, slower). edges: draw triangle edges over filled faces.

Returns {png_base64, width, height, view, vertices, triangles}.

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": {
      "handle": "<handle>"
    },
    "name": "render_view"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNoiso
edgesNo
widthNo
handleYes
heightNo
workspaceNoRun this call in this named workspace
deflectionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds genuinely new context: the deflection/speed tradeoff and the exact return payload keys. It stops short of stating prerequisites (e.g., that handle must reference an existing shaped object) or workspace/document context requirements.

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 one-line purpose, then compact per-parameter notes and a single-line return summary; no filler. Slightly fragmentary formatting but every line carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The return shape is spelled out, which compensates for the absent output schema. But for a 7-parameter tool the description omits what 'handle' is, what defaults apply for width/height, and any document/workspace prerequisite, leaving real gaps.

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 description coverage is only 14%, so the description must carry the load, and it does add meaning for view (enumerating 'iso'|'top'|... which the schema does not), deflection (mm units and mesh/speed tradeoff), and edges. However the required 'handle' parameter, plus width and height, are left completely undefined.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (render), resource (a shaped object's view), and output format (PNG), plus the projection types supported. It does not, however, distinguish itself from close siblings such as render_views, render_photoreal, section_view, or add_thumbnail, so an agent must infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance, and no sibling is named as an alternative despite a large render/export family. The only usage signal is implicit in the parameter notes (e.g., choosing a view direction).

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

Deploy Server

Other Tools