Skip to main content
Glama
FreeCAD Tutor MCP
by alex-r-t

pocket_sketch

Cuts material from a PartDesign Body by creating a Pocket from a selected sketch, with undo and automatic rollback if the operation is invalid.

Instructions

Cut material from a PartDesign Body using Pocket (undoable; rolls back if invalid).

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": {
      "sketch_name": "<sketch_name>"
    },
    "name": "pocket_sketch"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
lengthNo
doc_nameNo
reversedNo
sketch_nameYes
through_allNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly=false, destructive=false, idempotent=false, so the safety profile is given. The description adds real value by disclosing that the operation is undoable and rolls back when invalid, which explains why destructiveHint is false for a material-removal tool. However, it says nothing about required state (active body, sketch profile validity) or what failure looks like.

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 with zero padding; the operation and its transaction semantics are packed into one clause plus a parenthetical. Every element earns its place.

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

Completeness2/5

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

An output schema exists, so return values need not be described, and annotations cover the safety profile. But for a 6-parameter mutation, the definition omits prerequisites and every parameter's meaning, leaving the agent under-equipped to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 6 parameters, and the description supplies no parameter meaning at all — length, through_all, reversed, name, and doc_name are entirely undocumented, including non-obvious booleans and a defaulted numeric depth. It does not compensate for the coverage gap in any way.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('cut material') on a specific resource ('a PartDesign Body') via a named feature type ('Pocket'), so an agent can immediately tell it is a subtractive counterpart to a pad operation. It does not explicitly name or contrast a sibling tool such as pad_sketch, which keeps it short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies usage (cut material from a body) but gives no when-to-use/when-not conditions and no prerequisites — nothing about needing an active body, a sketch attached to a face, or existing material to cut into. The agent must infer all preconditions.

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