Skip to main content
Glama

Molding Pack Check

pack_check
Read-only

Check whether a part fits a shipping carton with reorientation, then calculate dimensional and billable weight to validate packaging and shipping cost.

Instructions

Check a part against a shipping carton + compute billable weight. part_bbox_mm/carton_mm are [l,w,h] mm; fits allows reorientation (sorted-dim compare). void_fraction = 1−vol(part)/vol(carton); dim_weight_kg = vol(carton cm³)/dim_factor (default 5000 metric DIM); billable_weight_kg = max(actual, dimensional). Returns {fits, void_fraction, dim_weight_kg, actual_mass_kg, billable_weight_kg, pass}.

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": {
      "part_bbox_mm": "<part_bbox_mm>",
      "carton_mm": "<carton_mm>",
      "mass_g": "<mass_g>"
    },
    "name": "pack_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
mass_gYes
carton_mmYes
workspaceNoRun this call in this named workspace
dim_factorNo
part_bbox_mmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description goes further by disclosing the actual math — void_fraction = 1−vol(part)/vol(carton), dim_weight from carton cm³/dim_factor, and billable = max(actual, dimensional). It also notes that `fits` permits reorientation via sorted-dimension comparison, which is real behavioral context. It stops short of stating failure modes or unit-validation behavior.

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 primary purpose, then parameter conventions, then formulas, then the return shape — a logical ordering with no filler. The compressed phrasing ('sorted-dim compare') is economical but slightly telegraphic.

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?

With no output schema, the description compensates by enumerating all six returned fields, so an agent knows exactly what it gets back. For a 5-param read-only calculator this is nearly complete; only error/mismatch behavior is unaddressed.

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 description coverage is only 20% (only `workspace` is documented), so the description must carry the load — and it does, specifying that part_bbox_mm/carton_mm are [l,w,h] in mm and that dim_factor defaults to 5000 in the metric DIM convention. Residual gaps: mass_g is only implied to be grams by the name, and the array item typing isn't stated.

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?

States a specific verb and two resources — geometric fit against a carton plus billable-weight computation — which no sibling duplicates (envelope_check and moldability_check cover different problems). The 'shipping carton + billable weight' framing is distinctive enough to route an agent without opening the schema.

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 the usage context (packing/shipping a part into a carton) but never states when to call it versus alternatives such as envelope_check or cost_estimate, nor what it does not handle. A competent agent can infer usage, but the text gives no explicit routing guidance.

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

Deploy Server

Other Tools