laydyne.com WebMCP Tools, Schemas & Agent Capabilities

laydyne.com

live Unverified (seed import) Productivity & Business 64 tools imperative implementation

Describe your space and workflow to AI. Build layouts, adapt process scenarios, and compare simulations through MCP or the built-in assistant.

First seen 2026-10-05 · Last seen 2026-10-05 · Source: webmcp.com

Answer 27 · Act 33 · Transact 4 · Score: Not yet scored

Tool inspector

sweep_process_parameters

act imperative

Run a saved scenario at every combination of values of one or two of its parameters (openDocks 6, 8 and 10; staff by arrival rate), each point on the same seeds, without saving or resending the definition. Returns, per point, each measure's mean over the runs with its 95 % confidence interval (Student's t), and its difference from the baseline point paired run by run, with that interval and withinNoise (the interval takes in 0: these runs cannot tell the two apart). A value that is a bound (an elevator without cars) gives no difference. Requires a simulation subscription. Points left when its 20 s budget runs out are named in notRun: sweep them next. The shown result and comparison do not change; Studio shows the sweep in the simulation panel.

Page: /studio

Input schema

Property	Type	Required	Description
`expectedRevision`	string	yes	Use revision from the most recent get_space or successful edit.
`id`	string	yes	—
`parameters`	object	yes	One or two of the scenario's own parameters, each with the values to try ({"openDocks": [6, 8, 10]}); every combination is a point, at most 25 with the baseline, and points × runs at most 500.
`baseline`	object	no	The point differences are taken from (values of the swept parameters); the scenario's own values when left out. It is run too when not among the points.
`runs`	integer	no	Runs per point, on seeds seed, seed + 1, … at every point (the scenario's runs when left out). Intervals need 2 or more; 5 to 20 is usual.
`measures`	array	no	Measures to report by key (an id such as run.wait.mean, or id:ref such as resource.wait.mean:docks; an id alone takes all its refs). Left out: the run measures and those of the resources and pools the swept parameters set.
`operationId`	string	no	Your own unique name for this change, such as a UUID; optional. Sending the same call again with the same operationId returns the earlier result (replayed: true) instead of applying it twice, and get_operation tells whether it applied. Use a new one for each new change.
`requestGroupId`	string	no	Attach this live edit to an open request group. Requires a fixed operationId and the current owned expectedRevision. Only the advertised five editing tools support groups.

Raw JSON schema

{
  "type": "object",
  "properties": {
    "expectedRevision": {
      "type": "string",
      "minLength": 1,
      "maxLength": 80,
      "description": "Use revision from the most recent get_space or successful edit."
    },
    "id": {
      "type": "string",
      "pattern": "^[A-Za-z0-9][A-Za-z0-9_-]{0,63}$"
    },
    "parameters": {
      "type": "object",
      "propertyNames": {
        "type": "string",
        "pattern": "^[A-Za-z0-9][A-Za-z0-9_-]{0,63}$"
      },
      "additionalProperties": {
        "minItems": 1,
        "maxItems": 25,
        "type": "array",
        "items": {
          "type": "number",
          "minimum": -1000000000,
          "maximum": 1000000000
        }
      },
      "description": "One or two of the scenario's own parameters, each with the values to try ({\"openDocks\": [6, 8, 10]}); every combination is a point, at most 25 with the baseline, and points × runs at most 500."
    },
    "baseline": {
      "description": "The point differences are taken from (values of the swept parameters); the scenario's own values when left out. It is run too when not among the points.",
      "type": "object",
      "propertyNames": {
        "type": "string",
        "pattern": "^[A-Za-z0-9][A-Za-z0-9_-]{0,63}$"
      },
      "additionalProperties": {
        "type": "number",
        "minimum": -1000000000,
        "maximum": 1000000000
      }
    },
    "runs": {
      "description": "Runs per point, on seeds seed, seed + 1, … at every point (the scenario's runs when left out). Intervals need 2 or more; 5 to 20 is usual.",
      "type": "integer",
      "minimum": 1,
      "maximum": 50
    },
    "measures": {
      "description": "Measures to report by key (an id such as run.wait.mean, or id:ref such as resource.wait.mean:docks; an id alone takes all its refs). Left out: the run measures and those of the resources and pools the swept parameters set.",
      "minItems": 1,
      "maxItems": 40,
      "type": "array",
      "items": {
        "type": "string",
        "minLength": 1,
        "maxLength": 120
      }
    },
    "operationId": {
      "type": "string",
      "pattern": "^[A-Za-z0-9][A-Za-z0-9._:-]{0,99}$",
      "description": "Your own unique name for this change, such as a UUID; optional. Sending the same call again with the same operationId returns the earlier result (replayed: true) instead of applying it twice, and get_operation tells whether it applied. Use a new one for each new change."
    },
    "requestGroupId": {
      "type": "string",
      "minLength": 1,
      "maxLength": 100,
      "description": "Attach this live edit to an open request group. Requires a fixed operationId and the current owned expectedRevision. Only the advertised five editing tools support groups."
    }
  },
  "required": [
    "expectedRevision",
    "id",
    "parameters"
  ],
  "additionalProperties": false
}