Skip to main content
Glama

ARCNM Nest Run Start

arcnm_nest_run_start
Destructive

Start a job nest that was kept as a draft — one created with arcnm_nest_run_create while this month's runs were used, which is stored, not queued, and never starts by itself. By default (apply=false) this only reads the job nest and says whether it is a draft and what starting it would nest. apply=true (needs parts:write) queues it: it spends one of this month's runs and is nested at today's stock and prices in the background — poll arcnm_nest_run_status, then read arcnm_nest_run_result. While the month's runs are still used, the start is refused and the job nest stays a draft. Only a draft starts, and only once; the same call within 24 hours answers the start it already made.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
applyNo
run_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
linesNo
copiesNo
groupsNoThe plan: each material and thickness it would nest.
run_idNoThe job nest started or kept as a draft; null for a plan of a new selection.
statusNoqueued once started; draft when kept, not queued, because this month's runs are used.
appliedYesTrue when the call wrote: the job nest was started, or kept as a draft (status 'draft'); false for a plan, which stores nothing.
guidanceYes
left_outNoThe plan: calculations of the batch or folder it would not take, each with why.
kept_as_draftNoThis month's runs are used: the job nest is (or, for a plan, would be) kept as a draft — stored, not queued, spending no run — until arcnm_nest_run_start starts it.
environment_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources