Skip to main content
Glama

view_sheet

Render a plan sheet or region as a PNG image for visual inspection, with optional overlays of committed shapes and a calibrated measuring grid for scale.

Instructions

SEE the sheet — render the page (or a crop of it) to a PNG image. This is your eyes on the plan, so CROP, DON'T SQUINT: the render downsamples to the px budget (≤2000 long side), which on an E-size sheet is ~4 sheet pixels per returned pixel — a full-sheet render finds WHERE things are, and only a tight region crop can tell you what the linework and labels actually say. Never audit a trace or read a dimension off a full-sheet render. region is in image px — the same space as every other tool — so a feature at pixel (ix, iy) of the returned image sits at x = region_x0 + ix × (region_x1 − region_x0) / img_w (same for y), and those coordinates go straight into one_click, measure_polygon, or read_sheet_text. overlay:true burns the session's committed shapes into the render (human-affirmed ink solid red, unreviewed machine shapes dashed blue) — render again after committing to verify your geometry landed where you intended, and sanity-check what you see: a fixture-sized ring where a room should be means the seed landed inside a stall or casework; an outsized ring means the flood escaped through an opening. To MEASURE rather than guess, pass grid: a calibrated measuring grid is burned in — thin lines every 1 ft, heavy blue every 5 ft, foot labels along the crop edges, feet counted from the crop's top-left corner. Count grid cells between walls exactly like an estimator scaling a plan; never derive a dimension by eye when the grid can give it to you. grid "auto" uses the sheet's set scale; before set_scale, pass the drawing scale read off the title block as inches-per-foot — "1/4" for a 1/4" = 1'-0" plan, "3/16", "0.25". Rendering needs the optional native canvas (@napi-rs/canvas); where it isn't installed this tool errors cleanly and every other tool still works. Coordinates are image px at render scale 2.0: PDF pt × 2, origin top-left, y down (the browser canvas's native space). Sheet payloads carry dims in both px and pt.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pxNoLong-side pixel budget of the returned image (default 1400) — small region + high px = readable dimension strings
gridNoBurn in a calibrated 1-ft/5-ft measuring grid: "auto" = the sheet's set scale; otherwise the drawing scale as inches-per-foot, e.g. "1/4", "3/16", "0.25"
sheetYes
regionNoCrop rect in image px (origin top-left, y down); omit for the full sheet
overlayNoBurn committed shapes into the render (solid = human-affirmed, dashed = unreviewed)
Behavior5/5

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

No annotations are provided, so the description fully carries the burden. It discloses downsample behavior (px budget, sheet pixels per returned pixel), coordinate system (image px, scale 2.0, origin top-left, y down), overlay semantics (solid red vs dashed blue), grid behavior (thin/heavy lines, labels, scale), and the optional-canvas dependency with graceful failure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Though lengthy, the description is densely packed with essential guidance and no filler. It front-loads the core purpose, then logically progresses to cropping strategy, coordinate mapping, overlay usage, grid measurement, and dependencies. Every sentence contributes actionable information for a complex tool.

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?

The tool has no output schema, so the description must explain what is returned and how to interpret it. It specifies the return is a PNG image, covers pixel budgets, cropping, coordinate mapping, overlay verification, and grid calibration. For a rendering tool with this complexity, the description is complete and self-sufficient.

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?

Despite 80% schema coverage, the description adds substantial meaning beyond the schema: it explains the pixel-coordinate conversion formula for region, interprets grid values like '1/4' and '0.25', clarifies the overlay's color/dash semantics, and specifies px as the long-side budget. This transforms each parameter from a bare property into an operationally meaningful control.

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 opens with a specific verb and resource: 'render the page (or a crop of it) to a PNG image.' It clearly positions this tool as the visual/eyes-on-the-plan tool and distinguishes it from siblings like read_sheet_text by noting where its output feeds into those other 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?

The description gives explicit guidance: crop rather than full-sheet for auditing, never read dimensions off a full-sheet render, use grid to measure, and pass coordinates to one_click, measure_polygon, or read_sheet_text. It also explains when to use grid 'auto' vs a manual scale and warns that non-installed native canvas still allows other tools to work.

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/Kentucky-ai/opentakeoff'

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