Skip to main content
Glama

Pocket

pocket

Cuts a length-defined recess from a body by subtracting material from a sketch, with through-wall/body and direction controls to target the intended wall.

Instructions

Subtract a pad of length mm from the body. through_all ignores length.

through ('wall'|'body'): preferred over through_all. 'wall' ray-casts to the first exit and cuts exactly one wall — right for solids AND shelled bodies; 'body' (legacy ThroughAll) punches every wall of a shell. Implies direction='into_body'; result carries wall_depth_mm. direction ('into_body'|'away_from_body', preferred over the legacy raw reversed, honoured only when neither is set): the tool probes both Reversed values and picks the one that does / does not remove material. strict: raise instead of warn on a degenerate pocket.

Returns {handle, name, volume, removed_volume, volume_ratio}, plus warnings ONLY when the pocket removed the whole body or nothing (strict=True makes those errors). direction='away_from_body' never warns.

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": "<sketch>"
    },
    "name": "pocket"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoPocket
lengthNo
sketchYes
strictNo
throughNo
reversedNo
directionNo
workspaceNoRun this call in this named workspace
through_allNo

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. Changed1 schema field changedv0.5.5
    • addedInput schema / properties / strict
      Added value: +{
      +  "default": false,
      +  "title": "Strict",
      +  "type": "boolean"
      +}
  3. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations only set readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the description does the heavy lifting: it discloses that material is removed, that `strict` converts degenerate outcomes into exceptions, and exactly when `warnings` appears. It also declares the return payload, which the absence of an output schema makes essential.

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?

The core action is front-loaded and each subsequent block maps to a real decision the caller must make (through, direction, strict, return shape). It is dense and jargon-heavy with hard-wrapped lines, but no sentence is pure 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 9-parameter modelling tool with no output schema, the description covers return fields, warning conditions, and legacy-parameter handling well. The remaining gap is the required `sketch` argument — its expected handle/format is never stated.

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 coverage is only 11%, so the description must compensate, and it largely does: it defines `length`, `through`, `through_all`, `direction`, `reversed` and `strict` semantics including precedence rules. The required `sketch` parameter and `workspace`/`name` are left undocumented, which keeps it from a 5.

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?

The opening sentence gives a specific verb and resource — subtract a pad of `length` mm from the body — which an agent can immediately distinguish from `pad` (additive) and from boolean/primitive tools. It does not explicitly name a sibling it replaces, so 4 rather than 5.

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?

Strong guidance on the parameter-level forks: `through`='wall' vs 'body' with the legacy `through_all` explicitly deprecated, and `direction` preferred over the raw `reversed` with the probing behavior described. What it lacks is tool-selection guidance against neighbours like `hole` or `boolean_op`, which is why it stops short of 5.

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