formlabs-local-mcp

save_form

Destructive

Save the active scene to a .form file at a specified absolute path. Confirm whether the target file already exists, since overwrite happens silently without warning.

Instructions

Save the scene as a .form file at an absolute path. Overwrites silently, so confirm with the user first if the file already exists.

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": {
      "file": "<file>"
    },
    "name": "save_form"
  }
}

Input Schema

Name	Required	Description	Default
`file`	Yes
`scene_id`	No	Scene id; omit for the default scene	default

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.4Sep 16, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already mark the tool as destructive, but the description adds crucial specificity: it overwrites silently and the agent should confirm with the user first if the file exists. This clearly discloses what gets destroyed without contradicting 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?

Two short sentences with no wasted words. The core action is front-loaded and the safety caveat follows naturally.

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?

For a simple two-parameter tool with one required parameter and no output schema, this description covers the action, target format, path requirement, and destructive overwrite behavior. No critical operational fact is missing.

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?

The schema documents scene_id but leaves 'file' as a bare string. The description compensates by clarifying that the file parameter expects an absolute path to a .form file, adding meaning beyond the schema.

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?

States a specific action ('Save the scene'), target format ('.form'), and path constraint ('absolute path'). This makes it easy to distinguish from load_form and the other scene-management tools without opening the schema.

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

Usage Guidelines3/5

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

The intended use is implied: this is the tool for saving a scene to a .form file. However, it does not explicitly name alternatives or state when not to use it, such as when loading a .form file instead.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.