Skip to main content
Glama

Sheet Base

sheet_base

Creates a sheet-metal base flange by extruding a closed straight-sided profile to a specified thickness, returning a handle for downstream flanges, flat patterns, and DXF export.

Instructions

Start a sheet-metal part: the base flange, a closed straight-sided profile extruded to thickness_mm. Everything else (flanges, tabs, hems, the flat pattern, the DXF) hangs off the handle this returns.

profile: [[x, y], ...] in the XY plane, implicitly closed. sketch: alternatively a handle to a closed, planar, straight-sided sketch — on any plane. Arcs are REJECTED rather than silently faceted, because a faceted flat pattern is a wrong flat pattern. material: any Materials-DB name (e.g. "Steel-A36", "AL6061-T6", "SS304"); it selects the K-factor and minimum-bend-radius corpus rows.

IMPORTANT — the profile is the flat face TANGENT TO TANGENT, not the outside dimension. Bends grow OUTWARD from the profile boundary, exactly as a base flange behaves in any sheet-metal CAD, so a U-channel of 100 mm outside width with R = t = 2 starts from a 92 mm profile.

The bend model lives alongside the handle for the life of the worker session, like every other handle: unfolding is a property of the FEATURE TREE, not of the fused solid, so a part reopened from disk in a new session is a solid rather than a sheet part. Cutting one (boolean_op cut, e.g. to drill it) keeps it a sheet part; fusing arbitrary material onto it does not.

Returns {handle, name, volume, thickness_mm, material, profile, area_mm2}.

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": {
      "thickness_mm": "<thickness_mm>"
    },
    "name": "sheet_base"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoSheetBase
sketchNo
profileNo
materialNo
workspaceNoRun this call in this named workspace
thickness_mmYes

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?

Annotations only cover the safety profile (readOnly=false, destructive=false, openWorld=false); the description supplies the behavioral context that matters: arcs are REJECTED rather than silently faceted, the bend model is bound to the worker session and lost on reopen from disk, and cut-vs-fuse have different effects on sheet-ness. The tangent-vs-outside-dimension rule (100 mm U-channel starting from a 92 mm profile) is exactly the kind of non-obvious behavior an agent could not infer from any structured field.

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?

Front-loaded with the one-line purpose, then the two input modes, then the geometric gotcha, then session semantics, then the return shape — a sensible ordering with no filler. It runs long for a tool description, and the session-lifetime paragraph could be tightened, but every sentence carries information an agent would otherwise get wrong.

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

Completeness5/5

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

For a mutation tool with no output schema and 17% schema coverage, the description closes both gaps: it spells out the return object (handle, name, volume, thickness_mm, material, profile, area_mm2) and warns about the session-bound feature tree. Nothing an agent needs to invoke this correctly and interpret the result 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?

Schema description coverage is only 17%, so the description has to carry the parameters, and it does: profile format and implicit closure, sketch handle requirements (closed, planar, straight-sided, any plane, no arcs), material as a Materials-DB name that selects K-factor and minimum-bend-radius rows, and thickness_mm as the extrusion depth. Only 'name' and 'workspace' go unmentioned, which is a minor gap given workspace has a schema description and name defaults sensibly.

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 ('Start a sheet-metal part: the base flange, a closed straight-sided profile extruded to thickness_mm') and makes clear this is the root feature from which sheet_flange/sheet_tab/sheet_hem and the flat pattern derive. An agent can distinguish it from the sibling sheet_* tools and from pad without opening any schema.

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?

It routes the agent between the two entry modes ('profile: [[x,y],...]' vs 'sketch: alternatively a handle to a closed, planar, straight-sided sketch'), and gives a downstream rule of thumb (boolean cut keeps it a sheet part; fusing arbitrary material does not). What it lacks is an explicit statement of when to pick sheet_base over pad or make_sketch, or a note that this must be called before the other sheet_* operations — that ordering is only implied by 'everything else hangs off the handle this returns'.

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