formlabs-local-mcp

get_scene

Read-only

Retrieve complete scene details for Formlabs printing: model IDs, bounding boxes, supports, print settings, material usage, and build volume. Specify a scene ID or use the default scene to get data.

Instructions

Get a scene: its models (ids, bounding boxes, supports), print settings, material usage and build volume.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_scene"
  }
}

Input Schema

Name	Required	Description	Default
`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/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds the actual return scope, which is especially valuable since there is no output schema. It communicates that the operation is a safe read that summarizes a scene's contents, going 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?

A single, front-loaded sentence that states the action and enumerates the key returned data without fluff. Every phrase adds information an agent needs to understand the tool's scope.

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?

The tool is simple (one optional parameter, no output schema), and the description covers the main return categories. It is complete enough for an agent to call correctly, though it could mention default-scene behavior or error cases, but those are largely covered by the parameter schema and annotations.

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 100%: scene_id has a clear description and default. The tool description does not add parameter-level detail, but with full schema coverage the baseline of 3 is appropriate.

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 names a specific verb ('Get') and resource ('a scene'), then enumerates the returned content: models, bounding boxes, supports, print settings, material usage, and build volume. This distinguishes it from siblings like get_model, list_scenes, and update_scene without needing to open schemas.

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?

It is clearly a read-only retrieval tool for a single scene, so when to use it is implied. However, there is no explicit guidance about when to prefer get_scene over list_scenes or get_model, nor any exclusions or prerequisites.

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