Skip to main content
Glama

Craft Quantities: construction material calculators

Take off plan sheets: counts, lengths, areas per layer

plan_set_takeoff
Read-onlyIdempotent

Totals a set of drawing sheets as the plan takeoff does: each sheet with its own scale (from a known line, or pixels per mm), counts, lengths and areas read off them in the sheet's pixels, layers adding up across the sheets; returns each layer's total and each sheet's share in metric and US units, unscaled marks left out and named. Points in, no picture; not sized.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sheets": "<sheets>"
    },
    "name": "plan_set_takeoff"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoThe answer's language. en (the default): as ever. es or es-US: US Spanish — labels, units, result lines and the honest machine-translation label from the site's Spanish pages, Spanish words read in a question or a trade term, and links to the /es/ pages once the site publishes them (until then the links stay English). fr or fr-CA (Canadian French, /fr/) and pt or pt-BR (Brazilian Portuguese, /pt/): the same from the site's French and Portuguese pages, figures with a decimal comma; each link names the translated page only once that page is published, otherwise the English page.en
nameNoThe set's name (default Plan set).
detailNofull (the default): the whole answer. summary: the result lines, the citation line and the page only — fewer tokens to read.full
sheetsYesThe sheets, each with its scale and its marks. At most 500 marks and 20,000 points in all.
systemNoThe system lengths are read in (both are returned).metric
inputUnitsNoSend "base" to pass bare numbers on dimensioned inputs in base units (m, m², L, kg …), as the published test vectors are written. Without it a length, area or volume must carry its unit.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description discloses meaningful behavior: results are aggregated per layer across sheets, returned in metric and US units, and unscaled marks are omitted from length/area totals but named. It does not cover error handling or limits, but the annotations already lower that burden.

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 compact and front-loads the core action, with no wasted sentences. Its dense single-sentence structure and terse final fragment 'Points in, no picture; not sized' are efficient but slightly cryptic.

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?

For a nested, multi-sheet takeoff tool with a rich schema and an output schema, the description covers the essential behavior: per-sheet scaling, cross-sheet layer aggregation, units, and unscaled-mark handling. The main remaining gap is selection guidance versus closely related takeoff tools, which is more a usage-guideline issue.

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

Parameters3/5

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

Schema description coverage is 100%, so the input schema already documents scale forms, point formats, layer aggregation, units, and language/detail options. The description reinforces the takeoff model but adds little parameter-level meaning beyond what the schema provides.

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 states a specific verb and resource: it totals drawing sheets, reading counts, lengths, and areas by layer with per-sheet scale. It also clarifies 'points in, no picture; not sized', but it does not explicitly differentiate itself from siblings such as get_takeoff or run_takeoff.

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?

Usage is implied by 'Points in, no picture; not sized' and by the per-sheet scale requirements, suggesting this is for pre-extracted point data rather than images. However, there is no explicit when-to-use guidance, no when-not-to-use guidance, and no named alternative.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources