Skip to main content
Glama

kernelcad

by com.kernelcad

Get Latest Render

get_latest_render
Read-only

Render a project's current model server-side and return it as an inline image so you can SEE what you built. Use this after open_in_studio (or any /p/ link): call with that slug to inspect whether the build looks right. CRITICAL — the image is rendered from the MODEL on the server; it does NOT reflect the user's Studio camera, zoom, or screen. NEVER ask the user to rotate, zoom, pan, move the camera, close a slider, or change their view to help you see — you cannot affect their screen and it cannot affect this render. To see a different angle, call this tool again with a different view. By DEFAULT (omit view, or view:"all") it returns a CONTACT SHEET of all six canonical views in one labeled image — a 3×2 grid, top row [iso, front, right], bottom row [back, left, top] — so you can judge the model from every side regardless of its orientation (e.g. to find which side has the doors). Pass a single view (iso/front/back/left/right/top) for one large render of that angle. DETERMINISTIC: the same model + view always returns the same bytes — identical bytes are NOT a stale/lagging snapshot. If you changed the model, push it with open_in_studio FIRST, then re-render to see the change. The image is always current and never a blank capture. Colors and shading match Studio (same palette / base-material color). The slug is the capability: no OAuth for public/unlisted; private projects require the owner signed in. The PNG is base64-inlined as a real image block by default; pass paths_only: true for metadata only. No renderable geometry or a mesh failure → { ok: false, error, hint }, never a blank image.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesProject slug from open_in_studio/get_project/a /p/<slug> link. The slug is the capability — public/unlisted projects need no OAuth; private projects require the owner to be signed in.
viewNoView to render. Default "all" = a labeled contact sheet of every canonical angle (iso/front/back/left/right/top) — best for judging the whole model. Pass a single view name for one large render of that angle.
paths_onlyNoControls PNG delivery. Default false: base64-inline the rendered PNG so clients that cannot fetch a URL over HTTP (e.g. a sandboxed agent) can still see it. Set true to return only metadata (smaller response).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okNoWhether a render was produced.
hintNoNext-action hint when ok is false.
viewNoThe view that was rendered (when ok).
bytesNoPNG byte length (when ok).
errorNoError code when ok is false (e.g. "empty_geometry", "mesh_failed").
widthNoRendered image edge in px (when ok).
heightNoRendered image edge in px (when ok).
image_b64NoBase64-encoded PNG bytes, present when inlined (paths_only=false) and under the size cap.
truncatedNoSet when inline was requested but the PNG exceeded the size cap.

TDQS

A4.9/5.0
Behavior5/5

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

The description goes far beyond the readOnlyHint annotation by detailing key behaviors: server-side rendering independent of user's Studio camera, deterministic output (same model + view = same bytes), always current and not stale, error handling (returns error object, never blank image), and color/shading consistency. It explicitly addresses potential misconceptions about staleness and blank captures.

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 lengthy but well-structured with clear sections (CRITICAL, DEFAULT, DETERMINISTIC). Each sentence conveys important information without redundancy. However, some details (e.g., 'slug is the capability') could be more concise without losing clarity. Overall, effective use of space.

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?

Given the tool's complexity (3 parameters, output schema, annotations), the description is exceptionally complete. It covers purpose, usage pattern, behavioral details, error handling, and parameter semantics. The presence of an output schema means return values don't need explanation, and the description touches on error states. No gaps evident.

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

Parameters5/5

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

Although the schema covers all parameters with descriptions, the tool description adds critical context: the default 'all' view returns a labeled contact sheet with specified layout (3x2 grid), the deterministic behavior ties slug and view, and paths_only is explained in terms of use cases (sandboxed agents). This adds value beyond the schema definitions.

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's purpose: 'Render a project's current model server-side and return it as an inline image'. It explicitly distinguishes from asking users to change their camera view, which is a common confusion. The verb 'render' and resource 'project's model' are specific, and the mention of inline image differentiates from potential sibling tools like 'render_preview'.

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?

The description provides explicit usage guidance: 'Use this after open_in_studio (or any /p/<slug> link)'. It tells what NOT to do: 'NEVER ask the user to rotate, zoom, pan... you cannot affect their screen'. It also instructs to re-render after pushing changes and to call with different view for different angles. Alternatives like paths_only are explained.

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

All kernelcad toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

Tools are mostly distinct, with clear descriptions for each. However, there is some potential overlap between inspection tools like 'inspect' and 'mesh_summary', and between rendering tools 'render_preview' and 'get_latest_render', which could cause minor confusion.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern, making it predictable for an agent to infer functionality.

Tool Count2/5

44 tools is significantly higher than the typical well-scoped range of 3-15. While the domain is complex, the count feels excessive and could overwhelm an agent.

Completeness4/5

The tool set covers an extensive range of CAD operations including creation, inspection, rendering, export, and verification. Minor gaps exist, such as direct sketch editing tools, but overall it is comprehensive.

Resources