Skip to main content
Glama

Add Rib

add_rib

Creates a reinforcing rib or web inside a PartDesign Body by thickening an open sketch spine into a wall that fuses with surrounding material.

Instructions

Add a reinforcing rib/web inside a PartDesign Body by thickening an OPEN sketch spine (line, arc, or connected polyline; NOT a closed loop) into a wall that fuses with the surrounding material. The sketch plane sets orientation.

thickness: wall thickness mm (> 0). midplane: centre the wall on the spine (default) or grow one side. reversed: flip if the rib lands on the wrong side of its sketch plane.

Returns {handle (starts 'rib_'), name, volume (the Body's mm^3 after — always greater), thickness}. Headless FreeCAD lacks PartDesign::Rib, so it is built as an equivalent midplane Pad of the offset spine; very intricate spines may differ. Raises ValueError on a closed/degenerate profile or thickness <= 0, RuntimeError if the rib adds nothing (spine does not span between walls).

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": {
      "body": "<body>",
      "sketch": "<sketch>",
      "thickness": "<thickness>"
    },
    "name": "add_rib"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
nameNoRib
sketchYes
midplaneNo
reversedNo
thicknessYes
workspaceNoRun this call in this named workspace

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 (readOnly=false, destructive=false, openWorld=false) by disclosing the implementation fallback ('Headless FreeCAD lacks PartDesign::Rib, so it is built as an equivalent midplane Pad of the offset spine'), the fidelity caveat for intricate spines, the additive guarantee on volume, and both ValueError and RuntimeError conditions.

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 core action and the critical open-spine constraint, then a compact per-parameter block, then return and error contract. Dense but nearly every clause carries information; the long opening sentence could be split for readability.

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 PartDesign tool with no output schema, the description supplies the return shape, the failure modes, and the geometric preconditions. The remaining gap is how the body and sketch are identified (handle vs name), which is left to a schema that is almost entirely undescribed.

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 14%, so the description must compensate, and it largely does: thickness, midplane, and reversed are each explained with semantics beyond their names, and sketch is constrained to an open spine. However body and the workspace/name parameters receive no explanation, leaving part of the 7-parameter surface undocumented.

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 ('Add a reinforcing rib/web inside a PartDesign Body') and immediately specifies the mechanism (thickening an OPEN sketch spine into a wall that fuses with surrounding material). This clearly distinguishes it from sibling modeling tools such as pad, pocket, revolve, or sweep.

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?

Explicitly states the key precondition (spine must be an open line/arc/polyline, NOT a closed loop) and that the sketch plane sets orientation, plus failure conditions. It stops short of naming alternative siblings (e.g. pad, thickness) and when to prefer them, so it is clear context without full alternative routing.

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