Skip to main content
Glama

Render Views

render_views
Read-only

Generates PNG views of a single 3D object from multiple angles, including isometric, top, and front, so you can inspect its geometry and layout.

Instructions

Render multiple views of a single object. Returns {views: {view_name: {png_base64,...}}}. Default views: ['iso', 'top', 'front'].

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_views"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewsNo
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

C2.9/5.0
Behavior3/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 usefully adds the response envelope shape ({views: {view_name: {png_base64,...}}}) and the default view set, but says nothing about image encoding cost, synchronous vs. queued rendering, or behavior on invalid view names.

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?

Three compact sentences, front-loaded with purpose then return shape then defaults; nothing is padded. Slightly dense with inline JSON, but every sentence carries information.

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

Completeness2/5

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

For a 6-parameter tool with 17% schema coverage and no output schema, the description leaves the meaning of handle, width/height resolution, and especially deflection ('deflection' of what?) unexplained, and gives no alternative-render routing. An agent can call it but cannot reason about parameter choices.

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 only 17% -- just the workspace parameter is documented. The description clarifies only 'views' (defaults iso/top/front), leaving width, height, deflection, and handle without any explanation in either field. With 4 of 6 parameters effectively undefined, the description does not compensate for the coverage gap.

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 and resource ('Render multiple views of a single object') and quantifies scope with default views. The plural 'views' implicitly separates it from the sibling render_view, though the distinction is never made explicit; render_photoreal and render_fem_results are also unaddressed.

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?

No statement of when to use this versus render_view, render_photoreal, section_view, or render_fem_results, and no prerequisites such as whether the object handle must come from register_handle or an active document. Usage must be inferred from the name alone.

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