Skip to main content
Glama

export_takeoff

Export the takeoff canvas payload as JSON in the exact format OpenTakeoff autosaves, with optional file output.

Instructions

The full "opentakeoff.takeoff_canvas.v1" annotations payload — exactly what the app autosaves, importable by it. Returned inline; pass path to also write it to disk as JSON. 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
pathNoFile path to write the payload to
overwriteNoReplace the file at path even when it is not an OpenTakeoff export. Off by default: re-exporting over a previous export of your own already overwrites without this, so you only need it to deliberately destroy an unrelated file.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
unitsYes
schemaYes
shapesYes
sheetsYes
markupsYes
approvalsNoApproval-family records (#176) — the estimator's APPROVED seals and the agent's verdict marks {id, actor, ts, sheet_id, at:[nx,ny], shape_id?, text?}. Present only when any exist (the canvas payload's own convention), so a verdict-free export stays byte-identical
conditionsYes
last_groupYes
sheet_tabsYes
sheet_groupYes
project_nameYes
sheet_levelsYes
Behavior4/5

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

With no annotations, the description carries the full burden and discloses important behaviors: coordinate system (scale 2.0, origin top-left, y down), inline return vs disk write, and overwrite semantics (requires overwrite flag for non-OpenTakeoff files). It does not explicitly state that the takeoff data itself is unmodified, but export implies read-only.

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?

The description is a single, dense sentence packed with essential information. It is front-loaded with the core purpose and every clause contributes meaning, with no fluff or repetition.

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

Completeness4/5

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

The description adequately covers the payload format, coordinate system, optional disk write, and overwrite behavior. Since an output schema exists, return values are documented separately. Minor gap: no reference to sibling tools for comparison, but overall it is complete for a technical export tool.

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

Parameters4/5

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

The schema already provides high coverage (100%) for both parameters. The description adds value by clarifying that the payload is returned inline by default and that passing 'path' writes to disk, which explains the relationship between parameters and output beyond the schema's individual descriptions.

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?

The description clearly indicates the tool returns the full 'opentakeoff.takeoff_canvas.v1' annotations payload, which is the app's autosaved format. It distinguishes from siblings like export_report and import_takeoff by focusing on the raw canvas payload, but uses technical jargon that may obscure the simple 'export' action.

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

Usage Guidelines3/5

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

The description implies usage for exporting/backing up the annotations payload and optionally writing to disk. It does not explicitly compare with alternatives like export_report or mention when not to use this tool, so guidance is present but not fully explicit.

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