Skip to main content
Glama

capture_views

Render the active SolidWorks part or assembly to PNG screenshots in multiple views to verify geometry. Supports cut planes for internal details.

Instructions

Capturar vistas — render the active part OR assembly to PNG screenshots so you can SEE the model and verify geometry. Read-only.

ADVERTENCIA (privacidad): las capturas se ENVÍAN a la API de Claude. Un screenshot puede mostrar logos, números de parte OEM o geometría confidencial. Decisión de piloto: el cliente usa su propia API key y firma el flujo de datos. Usa esta herramienta consciente de eso. [en: screenshots are SENT to the Claude API; pixels are NOT redacted.]

Cadence — render at CHECKPOINTS and at the END of a build, not after every feature: each call is one image per view (heavy tokens). Between features trust the cheap signals (mutator receipt.feature_count, batch summary); a final render before declaring a part done is mandatory (or bundle it via verify_build_report capture_view_names). Per-feature renders are for debugging a flaky build.

Args: views: subset of ["iso", "front", "top", "right", "trimetric"]. Default (None) = ["iso", "front", "top", "right"]. Unknown view name → ValueError (fail fast, no silent default). with_dims: accepted but a v1 NO-OP (dimension-annotation overlay needs a much larger surface). The param exists so the signature is stable. TODO(with_dims). section: optional {"plane": "front"|"top"|"right" (or Spanish UI name), "offset_mm": float} — render each view through a graphics CUT PLANE so INTERNAL cuts the outer silhouette hides (pockets, banded/saddle cuts, bores) become visible. offset_mm is signed from the standard plane (0 = through origin). Use this to diff against a drawing's SECTION view. Standard projections cannot show an occluded internal cut; for a purely internal feature an iso render proves nothing — also confirm it via list_faces.

Returns a list: one inline image per requested view (Claude sees them directly), followed by a summary dict with the resolved views, the local PNG paths, with_dims, and a privacy note.

Caveat: requires a part open in SolidWorks. Image bytes are NOT name-redacted (see ADVERTENCIA). Temp PNGs live in the OS temp dir and are read lazily when the result is serialized — they are not deleted by this tool.

Example — verify a base plate before drilling: extrude_sketch(25.0) capture_views(views=["iso", "front"]) # eyeball it get_bounding_box() # confirm extents

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
viewsNo
sectionNo
with_dimsNo
Behavior5/5

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

Discloses key behaviors: read-only, images sent to Claude API, no redaction, temp file persistence, requirement for open document, error on unknown view, and no-op parameter. Comprehensive for a tool with no 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?

Well-structured with sections (purpose, warning, cadence, args, returns, caveats, example). Slightly verbose with bilingual content but each sentence adds 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?

Comprehensive coverage including purpose, usage patterns, parameter details, return format, privacy/security, file handling, and example. Fully compensates for missing annotations and output schema.

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?

Explains all three parameters beyond schema: valid view names, default, error behavior; with_dims as no-op for future compatibility; section parameter with detailed effect and offset sign. Compensates for 0% schema coverage.

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?

Clearly states the tool renders active part or assembly to PNG screenshots for visual verification. Specifies read-only nature and distinguishes from mutation tools.

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 guidance on when to use (checkpoints/end of build) vs. not (after every feature), with alternatives like cheap signals and verify_build_report. Includes privacy warning and debugging use case.

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/danielproxd2/MCP_CAD'

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