Skip to main content
Glama
AstroQuestStudio

catia-v5-mcp

by AstroQuestStudio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

catia_drawing_add_view

Creates and places front, orthographic, isometric, section, or detail views in a CATIA V5 drawing from the 3D source, positioning each new view automatically near its reference or at specified sheet coordinates.

Instructions

Add one view of the 3D source to the drawing and place it. kind: front (the base view, create it first), top/bottom/left/right/rear (orthographic projections of the front view: 'right' = seen from the right of the front view), isometric, section, detail. Placement (position='auto', default): ISO 5456-2 arrangement from the plan of catia_drawing_create (first angle: top view BELOW the front, right view on its LEFT; third angle mirrored), else beside the parent in a free spot. Give position [x, y] (sheet mm, origin bottom-left, view CENTRE) to override. A view that would overlap another one or leave the frame is refused and removed. View coordinates (u, w), used by section/detail/dimensions, are millimetres at MODEL scale with the origin on the projection of the model origin; u to the right, w up. With view_from='-Y': front u=X, w=Z; top u=X, w=Y; right u=Y, w=Z; left u=-Y, w=Z; bottom u=X, w=-Y; rear u=-X, w=Z. section: give parent, cut_direction ('vertical' = cutting line x=cut_at, 'horizontal' = line y=cut_at, in the parent's (u,w)) or cutting_line [[u1,w1],[u2,w2]]; the tool draws the cutting-plane arrows, labels (A-A) and hatching; flip with side=1 if the wrong half is shown. detail: parent, centre [u,w], radius (mm, model scale), scale (default '5:1'). Returns JSON: view name, kind, scale, centre, paper box, origin, and the axes needed by catia_drawing_check.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindYes
sideNosection: which side is drawn.
labelNoView name (default: the kind, capitalised; CATIA appends A-A / A to section and detail views).
scaleNoView scale ('1:2', '5:1'); default the sheet scale (details default to '5:1'). A view whose scale differs from the sheet must be labelled (ISO 5455): CATIA prints it.
centreNodetail: circle centre [u, w] in the parent view (model mm).
cut_atNosection: u (vertical) or w (horizontal) of the cutting line.
gap_mmNoMinimum clearance between views (paper mm).
parentNoReference view for projections, section, detail (default: the front view).
radiusNodetail: circle radius (model mm).
sourceNoOpen CATPart/CATProduct (default: the one given to create).
drawingNoName of the CATDrawing document (default: the active document).
positionNoauto
view_fromNofront only: side the viewer stands on (default: from create, '-Y').
cutting_lineNosection: [[u1, w1], [u2, w2]] in the parent view (model mm).
hidden_linesNoShow hidden edges as thin dashed lines.
cut_directionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations declare the safety profile (non-readOnly, non-destructive, non-idempotent), and the description adds real behavioral context: overlapping/out-of-frame views are refused and removed, CATIA prints scale labels, CATIA appends A-A/A to section/detail names. It does not cover auth/preconditions or response side effects beyond the return JSON note.

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 kind list before the deeper placement/coordinate mechanics, and virtually every sentence carries necessary information. It is dense and long, but justified by the 16-parameter, multi-mode nature of the tool; a slightly lighter structure would be ideal.

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

Completeness5/5

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

With no output schema, the description compensates by naming the returned JSON fields (view name, kind, scale, centre, paper box, origin, axes for catia_drawing_check). Combined with the placement, coordinate and section/detail rules, an agent has everything needed to call it correctly.

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

Parameters5/5

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

Schema coverage is 81% (baseline 3), but the description goes well beyond it: it explains the ISO 5456-2 auto-placement rule and first/third-angle behavior, the sheet-mm centre-based position override, the (u,w) model-scale coordinate system with per-view_from axis mapping, and the section cut_direction/cutting_line semantics. This is substantive meaning the schema does not convey.

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 one view of the 3D source to the drawing and place it') and enumerates the exact kind options, so it is clearly distinguishable from siblings like catia_drawing_create or catia_drawing_add_dimension. The scope is unambiguous.

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 a clear ordering constraint ('front (the base view, create it first)'), and the kind list effectively documents which kind to pick for which purpose. It does not explicitly name alternative tools or when-not-to-use, so it stops short of a 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