Skip to main content
Glama

Add Section View

add_section_view

Adds a cross-section view when internal features such as counterbores or blind holes are ambiguous in outline or hidden-line views; auto mode checks the solid and skips if no hidden geometry exists.

Instructions

Add a cross-section view when the part has internal features the outline / hidden-line views convey ambiguously (counterbore, blind hole/bore, pocket). The need is judged from the real solid; the cut runs lengthwise through such a feature and the view is placed in clear space.

auto (default True): add it ONLY if hidden internal geometry exists, else return {added: False, recommended: False}; auto=False forces a section. process: 'auto' | 'prismatic' | 'turned' — how features are enumerated.

Returns {added, recommended, reasons, feature_ids, view?, normal?, origin?}. drawing_gate's section_recommended tells you in advance.

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": {
      "page": "<page>"
    },
    "name": "add_section_view"
  }
}

Input Schema

NameRequiredDescriptionDefault
autoNo
nameNoSection
pageYes
symbolNoA
processNoauto
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.0
Behavior4/5

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

Adds real behavior beyond the annotations: the no-op path returns {added: False, recommended: False} rather than erroring, the cut runs lengthwise through the detected feature, and the view is placed in clear space. It also enumerates the response shape. Annotations already cover the write/safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), so this is solid supplementary context.

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 core condition, then the auto/process semantics, then the return shape — a sensible order. Slightly dense with parenthetical asides, and the return-key list competes with the parameter block, but every line carries information.

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?

There is no output schema, and the description compensates by enumerating the return keys ({added, recommended, reasons, feature_ids, view?, normal?, origin?}). Combined with the auto-mode no-op explanation and the annotations, an agent has enough to call it correctly; only the page/naming parameters are under-described.

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 17%, so the description must carry the load: it explains `auto` semantics and default, and gives the valid `process` values ('auto' | 'prismatic' | 'turned') which the schema does not enumerate. `page`, `name`, and `symbol` are left to their titles, which is acceptable given how self-evident they are.

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 and resource (add a cross-section view) plus the geometric condition that justifies it (counterbore, blind hole/bore, pocket where outline/hidden-line views are ambiguous). The purpose is unmistakable, but it never explicitly distinguishes itself from the sibling tool `section_view`, which an agent could easily confuse with `add_section_view`.

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?

Gives clear selection criteria (internal features conveyed ambiguously) and explains the auto branch: auto=True adds only when hidden internal geometry exists, auto=False forces the section. It also points to `drawing_gate`'s `section_recommended` as a prior signal. It lacks an explicit 'do not use when' or a named alternative to `section_view`.

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