Skip to main content
Glama

Calculate embodied-carbon takeoff

calculate_takeoff
Read-onlyIdempotent

Calculate an auditable material takeoff from explicit geometry or a supported SmartScale/ProtoGen measurement payload. Returns net, explicit waste-adjusted, and conservative purchase quantities. This is a planning estimate, not a guaranteed material order or professional certification. If a call returns indeterminate, the response includes first_call_help. Example arguments: {"items": [{"id": "slab-1", "assembly": "concrete_slab", "unit_system": "imperial", "dimensions": {"length": {"value": "20", "unit": "ft"}, "width": {"value": "30", "unit": "ft"}, "thickness": {"value": "4", "unit": "in"}}}], "options": {}}

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "calculate_takeoff"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsNoThe items to quantify: a list of {id, assembly, unit_system, dimensions}. One item or a JSON string is also accepted.
optionsNoOptional. Extra settings for this call, as an object.
request_idNoOptional. Your id for this call. Repeat it to retry safely: the same request_id is never charged twice.
payment_refNoOptional. A paid credit or payment reference, used only after the free daily calls. Leave it out to use the free tier or a seat.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / items / description
      Added value: +"The items to quantify: a list of {id, assembly, unit_system, dimensions}. One item or a JSON string is also accepted."
    • addedInput schema / properties / options / description
      Added value: +"Optional. Extra settings for this call, as an object."
    • addedInput schema / properties / payment_ref / description
      Added value: +"Optional. A paid credit or payment reference, used only after the free daily calls. Leave it out to use the free tier or a seat."
    • addedInput schema / properties / request_id / description
      Added value: +"Optional. Your id for this call. Repeat it to retry safely: the same request_id is never charged twice."
  2. Changed2 schema fields changed
    • addedInput schema / $defs
      Added value: +{
      +  "TakeoffItem": {
      +    "additionalProperties": true,
      +    "description": "One thing to quantify: an assembly and its dimensions.",
      +    "properties": {
      +      "assembly": {
      +        "anyOf": [
      +          {
      +            "type": "string"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "default": null,
      +        "description": "What is being built. One of: aggregate_base, asphalt_shingle, brick_veneer, cmu_wall, concrete_column, concrete_footing, concrete_slab, concrete_wall, dimensional_lumber, drywall, excavation, paint, rebar_grid, sheathing, structural_steel, wood_wall_framing.",
      +        "examples": [
      +          "concrete_slab"
      +        ],
      +        "title": "Assembly"
      +      },
      +      "dimensions": {
      +        "anyOf": [
      +          {
      +            "additionalProperties": true,
      +            "type": "object"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "default": null,
      +        "description": "The measurements, each as {value, unit}. get_assembly names the dimensions an assembly needs.",
      +        "examples": [
      +          {
      +            "length": {
      +              "unit": "ft",
      +              "value": "20"
      +            },
      +            "thickness": {
      +              "unit": "in",
      +              "value": "4"
      +            },
      +            "width": {
      +              "unit": "ft",
      +              "value": "30"
      +            }
      +          }
      +        ],
      +        "title": "Dimensions"
      +      },
      +      "id": {
      +        "anyOf": [
      +          {
      +            "type": "string"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "default": null,
      +        "description": "Your label for this item; it is echoed in the result.",
      +        "title": "Id"
      +      },
      +      "unit_system": {
      +        "anyOf": [
      +          {
      +            "type": "string"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "default": null,
      +        "description": "One of: SI, imperial.",
      +        "examples": [
      +          "imperial"
      +        ],
      +        "title": "Unit System"
      +      }
      +    },
      +    "title": "TakeoffItem",
      +    "type": "object"
      +  }
      +}
    • changedInput schema / properties / items / anyOf
      Previous value: -[
      -  {
      -    "items": {
      -      "additionalProperties": true,
      -      "type": "object"
      -    },
      -    "type": "array"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "items": {
      +      "$ref": "#/$defs/TakeoffItem"
      +    },
      +    "type": "array"
      +  },
      +  {
      +    "$ref": "#/$defs/TakeoffItem"
      +  },
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  3. Changed5 schema fields changed
    • addedInput schema / properties / items / anyOf
      Added value: +[
      +  {
      +    "items": {
      +      "additionalProperties": true,
      +      "type": "object"
      +    },
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / items / default
      Added value: +null
    • removedInput schema / properties / items / items
      Removed value: -{
      -  "additionalProperties": true,
      -  "type": "object"
      -}
    • removedInput schema / properties / items / type
      Removed value: -"array"
    • removedInput schema / required
      Removed value: -[
      -  "items"
      -]
  4. Changed1 schema field changed
    • addedInput schema / properties / request_id
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Request Id"
      +}
  5. Changed1 schema field changed
    • addedInput schema / properties / payment_ref
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Payment Ref"
      +}
  6. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the bar is lower; the description still adds real value by disclosing the planning-estimate disclaimer, the three quantity variants returned, and the 'indeterminate' outcome with first_call_help. It does not describe cost/charging behavior in prose, though request_id retry semantics live in the schema.

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?

Front-loaded with the core action and outputs, then the caveat, then the failure mode, then a concrete example. The example line is long but earns its place for a nested-payload tool; no filler sentences.

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?

Output schema exists so return values needn't be spelled out, and the description covers scope, caveats, and the indeterminate path. The main omission is sibling routing (get_assembly for required dimensions), which is instead placed in the schema rather than the description.

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?

Schema coverage is 100%, so baseline is 3; the full example arguments object illustrates the nested dimensions {value, unit} shape and unit_system placement, which meaningfully reduces the chance of malformed calls. It does not explain what 'options' accepts beyond 'extra settings', so a small gap remains.

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?

States a specific verb and resource: 'Calculate an auditable material takeoff' from explicit geometry or a SmartScale/ProtoGen payload, and names the three quantity outputs. It does not differentiate itself from siblings like get_assembly or verify_result, and the title's 'embodied-carbon takeoff' framing diverges slightly from the description's 'material 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 context is implied by the inputs it accepts (geometry or measurement payload) and the indeterminate-response path is explained, but there is no explicit guidance on when to call this versus list_assemblies, get_assembly, or verify_result. The agent must infer that get_assembly should be consulted first for dimension requirements from text buried in the schema, not the description.

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.