A
licenseNot graded
qualityC
maintenancePlan optimal container & truck loads: 3D layouts, right-size the container mix, and check utilization, centre of gravity, crush protection and securing across 200+ equipment types.
17
MIT
Zhihuo RotoSpider Layout
Server Details
Rotomolding mold-on-arm layout feasibility: which molds fit on a machine arm/spider, and how.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4.4/5.0
Tool DescriptionsA
Average 4.6/5 across 2 of 2 tools scored.
Server CoherenceA
Disambiguation5/5
The two tools are completely distinct: check_mold_layout for layout verification and send_feedback for user communication. There is no overlap or ambiguity between them.
Naming Consistency5/5
Both tools follow a clear verb_noun pattern: check_mold_layout and send_feedback. The naming is consistent and predictable.
Tool Count3/5
With only two tools, the server feels thin for a domain-specific layout engine. The core functionality is confined to a single tool, and the feedback tool is generic, making the count borderline.
Completeness4/5
The check_mold_layout tool is comprehensive, covering machine presets, custom machines, various mold shapes, and outputs detailed results. Minor gaps exist, such as no separate tool for listing presets or retrieving machine specs, but the core domain is well covered.
Available Tools
2 toolscheck_mold_layoutARead-onlyIdempotentInspect
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).
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.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| molds | Yes | ||
| machine | No | ||
| arm_type | No | ||
| display_unit | No | mm | |
| response_api | No | rotospider.layout-check.v1 | |
| dead_height_in | No | ||
| dead_height_mm | No | ||
| include_layout | No | ||
| clearance_min_in | No | ||
| clearance_min_mm | No | ||
| riser_heights_in | No | ||
| riser_heights_mm | No | ||
| max_load_weight_kg | No | ||
| offset_spider_y_in | No | ||
| offset_spider_y_mm | No | ||
| spider_diameter_in | No | ||
| spider_diameter_mm | No | ||
| clearance_target_in | No | ||
| clearance_target_mm | No | ||
| envelope_diameter_in | No | ||
| envelope_diameter_mm | No | ||
| offset_horz_diameter_in | No | ||
| offset_horz_diameter_mm | No | ||
| allow_overhang_within_envelope | No |
Tool Definition Quality
A5/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and idempotentHint true, but the description adds substantial behavior: deterministic engine, 'never returns a physically invalid layout,' exact check types (rotation-envelope, dead-height, pairwise clearance, offset-arm riser selection), and unit conversion rules (converted once to micrometres, do not give both aliases). It also explains custom-mode switching and that display_unit 'in' adds a rounded projection. This goes far beyond the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is long but necessarily so for 24 parameters. It is well-structured: one-sentence purpose first, then engine explanation, then Args block with nested indentation, then Returns. Every sentence adds essential detail—no redundancy or fluff. The front-loading of purpose and the clear hierarchy make the length manageable.
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 tool with no output schema and zero schema descriptions, the description is remarkably complete. It covers all parameters, modes, defaults, unit aliases, return values (summary sentence plus per-arm results), and failure reason behavior. It even explains the response_api dialect options. There are no critical gaps.
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 description coverage is 0%, so the description carries the full burden. It documents every parameter: mold object shapes, machine presets, arm_type, all custom dimensions, decimal-inch aliases, defaults (clearance_target_mm 300, clearance_min_mm 150), and cross-parameter dependencies (e.g., custom offset requires offset_spider_y_mm). It even explains optional per-mold fields like name, weight_kg, quantity. Nothing is left ambiguous.
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+resource: 'Check whether molds fit together on a rotational-molding machine arm.' It clearly distinguishes this from the sibling send_feedback and explains the deterministic RotoSpider engine, making the tool's purpose unmistakable.
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?
Provides explicit usage guidance: when to leave machine empty to scan all presets ('which machine can take these molds?'), when to switch to custom-machine mode (giving spider_diameter_mm plus envelope_diameter_mm), when to choose straight vs offset arm, and how to select response_api dialects. This is more than typical guidance for alternatives—it maps out the decision tree for using the tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
send_feedbackAInspect
Relay a user question, bug report, or suggestion to the maintainers.
Args:
message: The user's feedback text (required).
contact: Optional reply address the user volunteers.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| contact | No | ||
| message | Yes |
Tool Definition Quality
A4.2/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations indicate non-readonly, and description confirms it relays feedback. No additional behavioral context (e.g., auth, rate limits) provided.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences plus Args list, efficient and no wasted words.
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?
Simple tool with two parameters; description covers their purpose adequately. No output schema, but return value is not critical for this action.
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 has 0% description coverage; description adds meaning for both parameters, explaining message is required and contact is optional reply address.
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?
Description clearly states the verb 'relay' and resource 'feedback to maintainers', distinguishing it from the sibling 'check_mold_layout'.
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?
Explicitly lists when to use (user question, bug report, suggestion) but lacks when-not-to-use or alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables 2D irregular polygon nesting (bin-packing) with tools to design, preview, get reports, and export DXF files for laser cutting or CNC routing.MIT
- FlicenseAqualityAmaintenanceCross-OEM industrial machine intelligence. Normalizes telemetry across 16 manufacturer families (Fanuc, Siemens, Haas, DMG Mori, Mazak), enables plain-English operational automation, and produces tamper-evident work records. 14 MCP tools.14
SmartCutofficial
FlicenseNot gradedqualityBmaintenanceSmartCut is a hosted cutting-optimisation API. It turns a list of parts and available stock into machine-ready cutting patterns for sheet materials (plywood, MDF, glass, plastic, sheet metal), linear stock (timber, bar, pipe, extrusion) and roll goods. Guillotine and true-shape nesting modes, with grain direction, per-part orientation locks, edge banding, blade kerf and stock trim.