Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

rest_initialize_host

Initializes a disposable Rest host for cloth simulation: open a saved .zprj copy, enable Pinching Simulation Override, poll status to completion, restore settings, and reopen the working project.

Instructions

Initialize the native Rest host in a fresh, minimized MD process.

Open a disposable saved .zprj copy and enable Pinching Simulation Override through the existing Rest tools first. Supply the SHA-256 of that copy. Simulation may change in-memory cloth positions. The tool never saves the project. Poll md_operation_status with the same request ID until settled, then restore the original Override value and reopen the working project.

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": {
      "scene_token": "<scene_token>",
      "scratch_project_sha256": "<scratch_project_sha256>",
      "request_id": "<request_id>"
    },
    "name": "rest_initialize_host"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idYes
scene_tokenYes
scratch_project_sha256Yes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations present, the description carries the full behavioral burden and does substantial work: it warns that simulation may change in-memory cloth positions, states the tool never saves the project, and requires polling until the operation settles. Missing are failure modes, permission/authentication needs, and what happens if the override is not restored, which keeps it below a 5.

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?

Purpose is front-loaded in the first sentence and the remaining lines are procedural steps, all of which carry information. The hard line breaks make it slightly harder to scan than a flowing paragraph, but there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a multi-step stateful operation with no annotations and no output schema, so the description must be self-sufficient, and it covers the workflow and side effects well. It still leaves gaps: the meaning of scene_token, what a successful result looks like before polling, and what to do if initialization fails.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It explains scratch_project_sha256 as the SHA-256 of the disposable copy and implies request_id is the correlation key for md_operation_status polling, but scene_token is never explained in either the schema or the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence gives a specific verb and resource: initialize the native Rest host in a fresh, minimized MD process. That is clearly distinct from siblings like rest_set_pinching_override or rest_adapter_inspect_host_controls, though the term 'native Rest host' is jargon an agent may not fully resolve from the description alone.

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 lays out a concrete prerequisite chain: open a disposable saved .zprj copy, enable Pinching Simulation Override via the existing Rest tools, then supply the SHA-256. It also names the follow-up tool (md_operation_status) and the post-condition cleanup (restore the original override, reopen the working project). It does not state when this tool should NOT be used, but the sequencing guidance is unusually explicit.

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