Skip to main content
Glama

Section View

section_view

Cuts a solid with a chosen plane to measure the exposed cross-section area, wire count, and bounding box without changing the input; optionally emits the profile wires as a new object.

Instructions

Cut a solid with a plane and measure the exposed cross-section — the way to "see inside" a part blind. Does not modify the input. mm / mm^2.

plane: "XY", "XZ", "YZ" (normals +Z, -Y, +X, as FreeCAD) or a datum-plane handle (its local +Z). offset: plane shift along its normal, mm (plane="XY", offset=10 cuts z=10). emit_profile: also add the section wires as a new registered object and return its handle (raises if the plane misses). Default: measure only. name: the emitted profile's name.

Returns {plane, offset_mm, normal, section_area_mm2 (closed wires), wire_count (0 = plane misses), closed_wire_count, bbox ({min, max, size} or None), handle?, name? (only with emit_profile)}.

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": {
      "handle": "<handle>"
    },
    "name": "section_view"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoSection
planeNoXY
handleYes
offsetNo
workspaceNoRun this call in this named workspace
emit_profileNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Adds meaningful behavior beyond annotations: the input solid is not modified, emit_profile creates a new registered object, the plane-miss failure mode is disclosed, and default behavior is measure-only. This clarifies why readOnlyHint is false despite the non-destructive input semantics.

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?

Front-loads the core operation, then gives compact per-parameter notes and a return summary. The description is dense but every line carries useful information for invoking the tool correctly.

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?

Given no output schema, the description supplies a detailed return shape including section area, wire counts, bbox, and optional handle/name. It is nearly complete for a complex sectioning tool, though the required handle parameter and workspace semantics are left implicit.

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?

Richly explains plane options and normals, offset semantics with a concrete example, emit_profile side effects, and name usage. With only 17% schema description coverage, this compensates well, though handle and workspace are not described in the tool text.

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 verb and resource: cut a solid with a plane and measure the exposed cross-section. The phrase 'see inside a part blind' gives an immediate mental model, and the units clarify the output domain. It is distinguishable from generic measurement and drawing-view siblings.

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?

Explains the intended use case clearly ('see inside' a part) and notes that it does not modify the input, with a default of measure-only. It does not explicitly compare against nearby alternatives such as add_section_view, but the context is strong enough for correct selection.

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