Skip to main content
Glama

Release Package

release_package
Destructive

Build a vendor/RFQ deliverable bundle for one item revision (STEP, drawings, BOM, inspection, checksummed manifest) only after lifecycle and revision gates pass.

Instructions

Produce the vendor/RFQ deliverable bundle for one item at one revision — STEP + drawings + BOM + inspection package + a checksummed manifest — gated by the item's lifecycle state and stamped with its ECO.

Every piece of this exists as its own tool. What this adds is the guarantee that ties them together: the STEP, the PDF, the BOM and the title block all describe the SAME revision of the SAME item. That is the whole point of a release, and it is enforced BEFORE a single file is written:

  • the item must be in a releasable lifecycle state (released), or draft must be set — which watermarks EVERY artifact PRELIMINARY (burned into the drawing, and carried as a format-legal comment in the STEP header, the DXF and the CSVs). An obsolete item is refused in both modes.

  • drawing_gate must pass for every included page — with require_ballooned when the inspection kind is requested.

  • the title block's part number / revision / material must MATCH the items registry. A mismatch is a FAILURE carrying expected-vs-actual, never a silent fix: quietly rewriting the print would destroy the only independent check that it and the model describe the same thing.

A refused release writes NOTHING — no half-populated directory a build script could mistake for a package.

registry / item: the items.json sidecar and the item id being released. out_dir: where the bundle is written (created if absent). kinds: any of "step", "drawing_pdf", "drawing_svg", "drawing_dxf", "bom_csv", "inspection", "manifest_json". Default step/drawing_pdf/drawing_dxf/ bom_csv/manifest_json. manifest_json is always added; inspection (ballooned print + plan + blank AS9102 form) implies a drawing kind. draft: cut a PRELIMINARY package from an unreleased item. rfq: the quote flavour — adds quantity breaks and the cost_estimate rollup as a quote-COMPARISON baseline (fidelity "correlation", band_pct 100 — trust the ratios, not the dollars) and drops internal-only artifacts (the inspection package, which states your acceptance criteria). eco: the change order this release is cut under; defaults to the item's metadata.eco. Stamped into the manifest AND the title block's REV cell. pages: page handles/names/labels (default: every page in the document). handle / object: the geometry to export (default: the first page's main view source — literally the solid the drawing dimensions). process: drawing_gate process ("auto" | "prismatic" | "turned"). density / recursive: BOM options, as in bom_extract. quantity_breaks / cost_process / material: RFQ pricing inputs (default [1, 10, 100], "cnc", and the item's declared material).

Determinism: the same item at the same revision produces a BYTE-IDENTICAL package. The exporters' wall-clock header stamps (the STEP FILE_NAME timestamp above all) are scrubbed to a fixed epoch, so a re-released package is diffable by checksum.

Returns {ok, dir, item, part_number, rev, lifecycle, eco, material, draft, watermark, flavor, kinds, dropped_kinds, implied_kinds, pages, files:[{name, kind, bytes, blake2b}], manifest, manifest_path, verify, problems}. ok=False means the gate refused and nothing was written; each problem carries {code, where, field, expected, actual, reason}.

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": {
      "registry": "<registry>",
      "item": "<item>",
      "out_dir": "<out_dir>"
    },
    "name": "release_package"
  }
}

Input Schema

NameRequiredDescriptionDefault
ecoNo
rfqNo
itemYes
draftNo
kindsNo
pagesNo
handleNo
objectNo
densityNo
out_dirYes
processNoauto
materialNo
registryYes
recursiveNo
workspaceNoRun this call in this named workspace
cost_processNocnc
quantity_breaksNo

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.9/5.0
Behavior5/5

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

Annotations (destructiveHint=true, readOnlyHint=false) are consistent and the description adds substantial context beyond them: a refused release writes NOTHING, mismatches fail with expected-vs-actual rather than silent fixes, draft watermarks every artifact PRELIMINARY, and identical input yields a byte-identical package due to scrubbed timestamp headers. These are exactly the preconditions and side effects an agent needs before invoking a destructive write.

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 purpose and the guarantee, then gate rules, then a compact per-parameter block, then determinism and return shape — a sensible order with little filler. It is long, and a phrase like 'That is the whole point of a release' is flourish, but the density of actionable content justifies nearly all of the length.

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?

For a 17-parameter destructive tool with no output schema and near-zero schema descriptions, the description supplies preconditions, per-parameter meaning and defaults, failure semantics, determinism guarantees, and the full return shape including the problem record structure. Nothing an agent needs to call it correctly or interpret failure is missing.

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?

Schema coverage is only 6% (just the workspace field), so the description carries the full burden — and it does, documenting registry/item, out_dir, kinds with the full valid value list and defaults, draft, rfq, eco with its default source, pages, handle/object with its default resolution rule, process, density/recursive, and the RFQ pricing inputs. That is meaningfully beyond what the bare schema reveals.

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+resource (produce the vendor/RFQ deliverable bundle for one item at one revision) and enumerates exactly what the bundle contains: STEP + drawings + BOM + inspection package + checksummed manifest. It explicitly differentiates itself from siblings ('Every piece of this exists as its own tool') and names the actual value-add — cross-artifact revision consistency — which no sibling like export_drawing or bom_extract provides.

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?

Gives explicit use conditions and exclusions: item must be 'released' or draft must be set, 'obsolete' is refused in both modes, drawing_gate must pass, and require_ballooned is needed for inspection kind. It also routes callers who only need one artifact back to the individual tools and explains the rfq flavour (drops internal-only artifacts) versus the default release.

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