Skip to main content
Glama

Zhihuo RotoSpider Layout

check_mold_layout

Read-onlyIdempotent

Check whether molds fit together on a rotational-molding machine arm.

    Every answer comes from the deterministic RotoSpider geometric layout
    engine: rotation-envelope and dead-height checks, pairwise mold-to-mold
    clearance, offset-arm riser selection, and ring arrangements for 3+
    identical molds. It never returns a physically invalid layout.

    Args:
        molds: List of mold objects. Use one explicit unit convention:
            Box/frame mold: {"length_mm": L, "width_mm": W, "height_mm": H}.
            Cylinder/tank mold: {"diameter_mm": D, "height_mm": H}.
            Exact L, slope, triangle, frustum, or complex mold: measured
            length_mm+width_mm+height_mm plus the complete
            geometry_asset_id+geometry_asset_revision returned by the
            geometry WebAPI or another trusted publisher.
            Decimal-inch aliases are length_in, width_in, height_in, and
            diameter_in. Each value is converted once to canonical
            micrometres; do not give both aliases for the same value.
            Optional per mold: "name", "weight_kg", "quantity" (default 1;
            use 0 to retain the mold type without requesting a copy).
        machine: Public-sample straight-arm preset. Available models are
            listed in the tool description. Leave empty AND give no
            explicit geometry to scan all presets ("which machine can take
            these molds?").
        arm_type: 'straight' (dual spiders) or 'offset' (single-spider
            offset/L arm). Empty = both.
        spider_diameter_mm: Custom machine - spider (mounting plate)
            diameter. Giving this plus envelope_diameter_mm switches to
            custom-machine mode instead of presets.
        envelope_diameter_mm: Custom machine - rotation envelope diameter
            (for offset arms: the vertical envelope diameter).
        dead_height_mm: Custom straight arm - unusable center height
            between the upper and lower spider surfaces.
        offset_spider_y_mm: Custom offset arm - spider Y offset from the
            spider center to the sphere center (required for custom offset).
        offset_horz_diameter_mm: Custom offset arm - horizontal usable
            envelope diameter after side trim (defaults to envelope).
        riser_heights_mm: Custom offset arm - available riser heights; the
            solver picks the best (or none).
        *_in: Decimal-inch aliases for the matching custom-arm and
            clearance *_mm arguments.
        max_load_weight_kg: Optional arm weight capacity; the solver loads
            molds only up to this total weight.
        clearance_target_mm: Target mold-to-mold clearance (default 300).
        clearance_min_mm: Minimum acceptable clearance (default 150).
        allow_overhang_within_envelope: Allow every mold shape to extend
            past the spider edge while its complete active shape remains
            inside the rotation envelope. Defaults to false.
        include_layout: Include request-relative mold placements. Use with
            response_api v1/v2/v3 to select the placement heading dialect.
        display_unit: 'mm' (default) or 'in'. Canonical result fields remain
            millimetres; 'in' adds a display projection rounded to 0.00001 in.
        response_api: Public placement dialect. Defaults to
            rotospider.layout-check.v1; request rotospider.layout-check.v2
            for exact four-heading orient keys when layouts are included.

    Returns a summary sentence plus per-arm results: feasible, placed vs
    requested counts (per mold type when available), selected riser height,
    spider utilization, center-of-gravity offset, achieved clearance, and
    the engine's reason when molds do not fit.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
moldsYes
machineNo
arm_typeNo
display_unitNomm
response_apiNorotospider.layout-check.v1
dead_height_inNo
dead_height_mmNo
include_layoutNo
clearance_min_inNo
clearance_min_mmNo
riser_heights_inNo
riser_heights_mmNo
max_load_weight_kgNo
offset_spider_y_inNo
offset_spider_y_mmNo
spider_diameter_inNo
spider_diameter_mmNo
clearance_target_inNo
clearance_target_mmNo
envelope_diameter_inNo
envelope_diameter_mmNo
offset_horz_diameter_inNo
offset_horz_diameter_mmNo
allow_overhang_within_envelopeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / include_layout
      Added value: +{
      +  "default": false,
      +  "title": "Include Layout",
      +  "type": "boolean"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / allow_overhang_within_envelope
      Added value: +{
      +  "default": false,
      +  "title": "Allow Overhang Within Envelope",
      +  "type": "boolean"
      +}
  3. Changed1 schema field changed
    • addedInput schema / properties / response_api
      Added value: +{
      +  "default": "rotospider.layout-check.v1",
      +  "title": "Response Api",
      +  "type": "string"
      +}
  4. Changed31 schema fields changed
    • addedInput schema / properties / clearance_min_in
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Clearance Min In"
      +}
    • addedInput schema / properties / clearance_min_mm / anyOf
      Added value: +[
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / clearance_min_mm / default
      Previous value: -150New value: +null
    • removedInput schema / properties / clearance_min_mm / type
      Removed value: -"integer"
    • addedInput schema / properties / clearance_target_in
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Clearance Target In"
      +}
    • addedInput schema / properties / clearance_target_mm / anyOf
      Added value: +[
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / clearance_target_mm / default
      Previous value: -300New value: +null
    • removedInput schema / properties / clearance_target_mm / type
      Removed value: -"integer"
    • addedInput schema / properties / dead_height_in
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Dead Height In"
      +}
    • addedInput schema / properties / dead_height_mm / anyOf
      Added value: +[
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / dead_height_mm / default
      Previous value: -0New value: +null
    • removedInput schema / properties / dead_height_mm / type
      Removed value: -"integer"
    • addedInput schema / properties / display_unit
      Added value: +{
      +  "default": "mm",
      +  "title": "Display Unit",
      +  "type": "string"
      +}
    • addedInput schema / properties / envelope_diameter_in
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Envelope Diameter In"
      +}
    • addedInput schema / properties / envelope_diameter_mm / anyOf
      Added value: +[
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / envelope_diameter_mm / default
      Previous value: -0New value: +null
    • removedInput schema / properties / envelope_diameter_mm / type
      Removed value: -"integer"
    • addedInput schema / properties / offset_horz_diameter_in
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Offset Horz Diameter In"
      +}
    • addedInput schema / properties / offset_horz_diameter_mm / anyOf
      Added value: +[
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / offset_horz_diameter_mm / default
      Previous value: -0New value: +null
    • removedInput schema / properties / offset_horz_diameter_mm / type
      Removed value: -"integer"
    • addedInput schema / properties / offset_spider_y_in
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Offset Spider Y In"
      +}
    • addedInput schema / properties / offset_spider_y_mm / anyOf
      Added value: +[
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / offset_spider_y_mm / default
      Previous value: -0New value: +null
    • removedInput schema / properties / offset_spider_y_mm / type
      Removed value: -"integer"
    • addedInput schema / properties / riser_heights_in
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "number"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Riser Heights In"
      +}
    • changedInput schema / properties / riser_heights_mm / anyOf
      Previous value: -[
      -  {
      -    "items": {
      -      "type": "integer"
      -    },
      -    "type": "array"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "items": {
      +      "type": "number"
      +    },
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / spider_diameter_in
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Spider Diameter In"
      +}
    • addedInput schema / properties / spider_diameter_mm / anyOf
      Added value: +[
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / spider_diameter_mm / default
      Previous value: -0New value: +null
    • removedInput schema / properties / spider_diameter_mm / type
      Removed value: -"integer"
  5. First observed

TDQS

A4.5/5.0
Behavior5/5

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

With readOnlyHint and idempotentHint already present, the bar is lower, yet the description adds substantial behavioral context: it is deterministic, never returns a physically invalid layout, converts inch values once to canonical micrometres, applies defaults such as clearance_target_mm=300 and allow_overhang_within_envelope=false, and explains result units. No contradiction with annotations.

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?

The description is long but appropriately structured with a purpose statement, an Args section, and a Returns section. It is front-loaded with the core intent. A few sentences are redundant or unfulfilled, notably the claim that machine models are listed, but overall the length is justified for 24 parameters.

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?

Given the tool's complexity, no output schema, and minimal annotations, the description provides a thorough account of parameters, unit conventions, modes, and return values. It falls short of a 5 because the machine preset names are referenced but not enumerated, and the response_api v1/v2/v3 distinction is only partially explained.

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 0%, and the description compensates well by documenting mold object shapes, inch aliases, unit conversion rules, custom-machine mode switches, defaults, and response dialect options. However, the machine parameter says available preset models are listed in the tool description, yet no such list is actually present, leaving a real gap for that parameter.

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?

The description opens with a specific verb and resource: 'Check whether molds fit together on a rotational-molding machine arm.' It then names the concrete checks performed (rotation-envelope, dead-height, pairwise clearance, riser selection), which leaves no ambiguity about the tool's function. It is also clearly distinct from the only sibling, send_feedback.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives strong usage context: when to scan all presets by leaving machine empty, when custom-machine mode is activated, and how arm_type and response_api affect behavior. It does not explicitly state 'when not to use' or name alternative layout tools, and it claims available machine models are listed but never actually lists them, which is a small guidance gap.

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.

Resources