Skip to main content
Glama
AstroQuestStudio

catia-v5-mcp

catia_drawing_add_centerlines

Draw ISO 128-2 centre lines through each circle centre in a CATIA drawing view, extending each line beyond the circle by extension_mm. Returns the number of lines created.

Instructions

Draw centre lines (thin chain lines, ISO 128-2 type 04.1) crossing at each given circle centre of a view, extending extension_mm (paper) beyond the circle. centres: [{u, w, radius}] in view coordinates. Returns the number of lines created.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
viewYes
centresYes
drawingNoName of the CATDrawing document (default: the active document).
extension_mmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare it is a write, non-idempotent, non-destructive operation. The description adds useful context: the exact line type, that extension_mm is measured in paper space beyond the circle, and that the return value is a count of created lines. It does not mention duplicate creation on repeat calls, though the non-idempotent annotation covers that behavior.

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?

Three short sentences/fragments, front-loaded with the action and line standard, followed by parameter semantics and return value. No redundant or filler text.

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 write tool with no output schema, the description covers the operation, the centre coordinate meaning, extension behavior, and return count. It omits explicit clarification of the required 'view' parameter's expected format and the drawing default, but these are minor given the schema and annotations.

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

Parameters3/5

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

Schema coverage is only 25%, so the description must compensate. It explains centres as [{u, w, radius}] in view coordinates and extension_mm as paper-space extension beyond the circle, but leaves the required 'view' and optional 'drawing' parameters unspecified.

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 ('Draw centre lines'), the resource (view circles), the line standard (thin chain, ISO 128-2 type 04.1), and the extension behavior. Clearly distinguishable from siblings such as catia_drawing_add_dimension or catia_drawing_add_view.

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

Usage Guidelines3/5

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

Implies usage for adding centerlines to circles in a drawing view, but gives no explicit when-to-use/when-not-to-use guidance or named alternatives. The agent must infer the operational context from the name and description.

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