CST-MCP

Overview Schema Source Related Servers Discussions Admin

cst_create_elliptical_cylinder_tool

Create an elliptical cylinder in a CST 3D model by specifying its axis, X and Y radii, component, and ranges for geometry construction.

Instructions

Create an elliptical cylinder.

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": {
      "component": "<component>",
      "name": "<name>",
      "axis": "<axis>",
      "xradius": "<xradius>",
      "yradius": "<yradius>",
      "ranges": "<ranges>"
    },
    "name": "cst_create_elliptical_cylinder_tool"
  }
}

Input Schema

Name	Required	Description	Default
`axis`	Yes
`name`	Yes
`title`	No
`center`	No
`ranges`	Yes
`xradius`	Yes
`yradius`	Yes
`material`	No
`segments`	No
`component`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Oct 1, 2026

TDQS

C2.3/5.0

Behavior1/5

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

No annotations are provided, so the description carries the full behavioral burden. It only restates the basic creation action and discloses nothing about side effects, required active context, coordinate conventions, error behavior, or persistence. It adds no behavioral information beyond the tool name.

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 description is a single front-loaded sentence with no wasted words. It is concise and structurally clean, though its extreme brevity reflects under-specification rather than an efficient summary of necessary details.

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

Completeness1/5

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

For a 10-parameter CAD creation tool with 0% schema description coverage and no annotations, this description is critically incomplete. It provides no parameter guidance, no behavioral context, and no usage conditions, even though an output schema exists and could have been referenced.

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?

The schema has 10 parameters with 0% description coverage, including 6 required parameters such as component, axis, xradius, yradius, and ranges. The description does not explain any parameter meaning, format, or constraints, leaving the agent with only bare titles.

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 description states a specific verb and resource: 'Create an elliptical cylinder.' The adjective 'elliptical' implicitly distinguishes it from the sibling cst_create_cylinder_tool, which likely creates a circular cylinder. However, it does not explicitly call out that distinction or describe scope, so it is clear but not fully differentiated.

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?

The description gives no guidance on when to use this tool versus alternatives such as cst_create_cylinder_tool or other primitive-creation tools. It also omits prerequisites like an active project or component. This is essentially no usage guidance.

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

Deploy Server