formlabs-local-mcp

load_form

Opens an existing .form file as a new scene. Provide an absolute file path to load it and get the scene back.

Instructions

Open an existing .form file as a new scene. file must be an absolute path. Returns the scene.

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": "load_form"
  }
}

Input Schema

Name	Required	Description	Default
`file`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.4Sep 16, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations indicate readOnlyHint=false and destructiveHint=false, so the description is not contradicting them. The description adds the constraint that 'file' must be an absolute path, which is useful behavioral context. However, it does not disclose what happens if the file does not exist, whether the current scene is replaced, or any side effects on the scene state.

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 two sentences with no wasted words. The key action and the critical parameter constraint are front-loaded, making it easy for an agent to parse quickly.

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?

Given the tool has only one parameter and no output schema, the description covers the essential action and the key parameter constraint. However, it lacks context about error conditions, side effects on the current scene, and whether this is a server-side file operation. For a tool that loads a file into a scene, an agent might need to know if the scene is replaced or if a new scene is created.

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 does add meaning by specifying that 'file' must be an absolute path and that it refers to a .form file. However, it does not explain the expected file format details, whether the path should be a local filesystem path or a server-side path, or any constraints on the file content.

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 description states a specific verb ('Open') and resource ('.form file as a new scene'), which clearly distinguishes it from sibling tools like save_form or create_scene. It could be slightly more explicit about the relationship to create_scene, but the core purpose is unambiguous.

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 description implies usage context: it is for opening an existing .form file, as opposed to creating a new scene or saving a form. However, it does not explicitly state when to use this tool versus alternatives like create_scene or import_model, nor does it mention any prerequisites (e.g., file must exist, server must be running).

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