Skip to main content
Glama

Sheet Tab

sheet_tab

Add a coplanar flat tab to a sheet-metal part along a free edge for mounting lugs, weld tabs, or snap-off features without introducing bends.

Instructions

Extend a sheet part with a coplanar tab — a flat ear off a free edge with no bend at all (a mounting lug, a weld tab, a snap-off).

Mechanically it is a zero-angle flange and shares that code path exactly: length_mm is how far the tab reaches past the edge, width_mm/offset_mm place it along the edge (default: the whole edge). It adds no bend to the bend report and no bend line to the DXF, but it does grow the flat pattern.

Returns the same dict sheet_flange does (angle_deg 0, inner_radius_mm 0).

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>",
      "edge": "<edge>",
      "length_mm": "<length_mm>"
    },
    "name": "sheet_tab"
  }
}

Input Schema

NameRequiredDescriptionDefault
edgeYes
nameNoSheetTab
handleYes
width_mmNo
length_mmYes
offset_mmNo
workspaceNoRun this call in this named workspace
feature_nameNo

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.5/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing non-obvious model side effects: no entry in the bend report, no bend line in the DXF, but the flat pattern does grow. It also states the return shape ('same dict sheet_flange does, angle_deg 0, inner_radius_mm 0'), which annotations alone (readOnlyHint=false, destructiveHint=false) cannot convey.

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-loads the definition and the sibling relation, then backs it with mechanics and return value; three short paragraphs, each earning its place. Slightly more prose than strictly needed for the return-value line, but no filler.

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 mutating, 8-parameter, no-output-schema tool the description covers purpose, side effects on downstream artifacts, and the return dict, which is unusually complete. Gaps remain on the edge reference format and whether a transaction_open/commit is required, which matter for a write operation in a codebase with explicit transaction siblings.

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 13%, so the description must carry the load, and it does for the parameters that matter geometrically: length_mm is 'how far the tab reaches past the edge', width_mm/offset_mm 'place it along the edge', with the default being the whole edge. It leaves handle, edge, name, and feature_name unexplained, so coverage of the full 8-parameter surface is incomplete but the non-obvious ones are well served.

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?

Opens with a specific verb and resource ('Extend a sheet part with a coplanar tab'), then defines what a tab is in physical terms (flat ear off a free edge, no bend). It also explicitly positions itself relative to sheet_flange as 'a zero-angle flange' sharing the same code path, which lets an agent distinguish it from the flange/hem siblings without opening a 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?

The 'no bend at all' framing and the examples (mounting lug, weld tab, snap-off) give a clear picture of when this tool applies, and the relation to sheet_flange implies the alternative. It stops short of an explicit 'use sheet_flange instead when you need a bend' routing statement, so the when-not is inferred rather than stated.

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