Skip to main content
Glama

export_report

Generate a computed takeoff report with per-condition quantities (gross/net), materials buy list, sheet subtotals, and scale provenance for pricing handoff.

Instructions

The computed Report document — "opentakeoff.report.v1", the same schema the canvas Report's JSON export writes. Everything a pricing consumer needs without re-implementing the app's math: per-condition quantities with waste and multiplier applied (gross and *_net), the computed materials BUY LIST per condition (order quantity = basis ÷ coverage rate, rounded up to whole purchase units) plus the project-wide roll-up summed by (name, unit), per-sheet BASE subtotals, scale provenance per sheet, and annotations. Contrast: export_takeoff is the raw canvas payload (materials as CONFIG rows, no computed quantities) and takeoff_summary strips materials for a compact reply — when the numbers are leaving for pricing, consume this. A report alone is HALF the deliverable: pair it with export_marked_pdf, because a takeoff is reviewed on marked drawings, not on numbers. Returned inline; pass path to also write it to disk as JSON.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoFile path to write the document to
project_nameNoLabel for the document's project_name field (a headless session has no project of its own; omitted → null)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
rfisYes
unitsYes
schemaYes
sheetsYesScale provenance per sheet — how each scale was set
totalsYes
markupsYes
by_labelYes
by_sheetYesBASE per-sheet subtotals — multiplier NOT applied, no waste, no materials
materialsYesProject-wide buy list — condition rows summed by (name, unit)
conditionsYesconditionTotals rows: gross + *_net quantities AND the computed materials buy list
roll_goodsYesRoll-goods order rows (#136) — order_lf / rolls / order_qty per roll-goods condition, ×N applied; empty when no condition carries a roll_setup (always the case for a headless session today)
project_nameYes
shape_labelsYes
display_unitsYes
generated_withYes
condition_columnsYes
Behavior4/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It explains the output contents in detail, notes that the report is returned inline, and discloses the optional file-write behavior via path. It does not explicitly state that it has no write side effects apart from the optional path, but the description implies a read/export operation and covers the main behavioral nuances.

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 long but dense with purposeful information: it lists report contents, defines the BUY LIST formula, differentiates from siblings, and gives pairing advice. Every sentence contributes value, though it could be slightly more scannable with shorter sentences. It is appropriately sized 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?

Given the tool's complexity, the description is thorough: it covers the exact schema, the computed fields, the contrast with related tools, the return behavior, and the recommended pairing. The presence of an output schema covers return structure, and the description fills in all needed behavioral and usage context.

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 covers both parameters at 100%, so the baseline is 3. The description adds meaningful context beyond the schema: it explains that path is for writing to disk as JSON, and that project_name is a label that is null in headless sessions. This extra semantic clarity justifies a score above baseline.

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 identifies the tool as producing the computed Report document in a specific schema, and explicitly contrasts it with sibling tools export_takeoff and takeoff_summary, distinguishing its role as the pricing-oriented export. The verb+resource is implied through the name and description, and the scope is unambiguous.

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?

It explicitly states when to use this tool ('when the numbers are leaving for pricing, consume this') and contrasts it with export_takeoff and takeoff_summary, including why those are different. It also instructs pairing with export_marked_pdf, providing clear alternative and complementary usage guidance.

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