Skip to main content
Glama

edit_materials

Add, remove, or patch coverage-rate rows on a finish condition, converting measured area or length into order quantities such as adhesive per gallon or grout per bag.

Instructions

Add, remove, or patch supporting-materials rows on a condition — the coverage-rate lines that turn a measured area/length/count into an order quantity (adhesive at N sf/gal, grout at N lf/bag, …), matching the canvas's per-condition Supporting Materials panel. Each row is {name, per, basis, unit, round, note}: quantity = the condition's basis total (area/linear/count/seam_lf) ÷ per, rounded up to whole purchase units unless round:false. basis "seam_lf" is the one basis that is FIGURED rather than measured: it is the length where two cuts meet on the floor, read off the condition's roll layout (set roll_setup with edit_condition), which is what a heat-weld rod or a carpet seam tape is bought by. A 20-ft-wide room off a 12-ft roll seams once down its length; the same square footage as two 10-ft rooms seams not at all, and no percentage of the area or the perimeter can tell those two jobs apart. Without a roll_setup — or with no committed floor shapes to lay out — a seam_lf row reads 0, which is the honest state rather than a guess. condition names an existing OR NEW finish tag (minted on first touch, same as one_click/measure_polygon) — add alone is enough to seed materials on a condition before you've traced anything. remove/patch target existing row ids from this reply or export_takeoff (takeoff_summary strips materials for a compact quantities-only reply); a bad id 404s the WHOLE call before anything is written, and referencing an id on a tag with no condition yet errors rather than silently minting an empty one. No review gate here — materials rows are quantity config, not traced geometry, so this edits directly; undo_last reverses a call in one step (the condition's whole materials array, snapshotted before the write, restored verbatim).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addNoNew rows to add
patchNoField changes on existing rows
removeNoExisting row ids to remove
conditionYesFinish tag, e.g. 'CPT-1'

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
changedYes
conditionYesThe finish tag passed in
materialsYesThe condition's full materials array after this write
condition_idYes
Behavior5/5

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

With no annotations, the description carries full burden and delivers: it discloses the no-review-gate direct edit behavior, whole-call 404 on bad ids, the error on missing condition, and the seam_lf reading 0 without roll_setup. It even includes a concrete example (20-ft vs 10-ft rooms) to explain the figured basis.

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 long but every sentence earns its place: it packs the purpose, formula, edge cases, error behavior, and tool relationships into one dense paragraph that is front-loaded with the action verb.

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 (add/remove/patch with six fields and a special basis), the description is remarkably complete: it covers formulas, edge cases, failure modes, and integration with edit_condition, undo_last, and export_takeoff. With an output schema present, return values need no explanation.

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 already covers all parameters at 100%, the description adds the calculation formula (basis ÷ per, rounded up), the meaning of round:false, the seam_lf special handling, and the minting of new tags on condition. This significantly enriches parameter understanding beyond the schema.

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 phrase 'Add, remove, or patch supporting-materials rows' and grounds the tool in the 'per-condition Supporting Materials panel,' clearly distinguishing it from sibling tools like edit_condition and takeoff_summary. It also explains the row structure and calculation, leaving no ambiguity about what the tool does.

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 context on when to use the tool: it is for 'quantity config, not traced geometry' and notes that undo_last reverses a call. It also contrasts with takeoff_summary ('strips materials') and directs users to edit_condition for roll_setup, making the relationship to alternatives clear.

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