Skip to main content
Glama
Sign In
CAD MCP Server

CAD MCP Server

by 652036
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

create_prism

Extrude a 2D profile entity by a specified height to generate a 3D prism, optionally assigning units and a layer.

Instructions

Create a prism from a 2D profile entity and height.

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": {
      "profile_id": "<profile_id>",
      "height": "<height>"
    },
    "name": "create_prism"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitNo
layerNo
heightYes
profile_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

There are no annotations, so the description carries the full behavioral burden. It says only that a prism is created, without disclosing whether the result is a solid or surface, how the profile is treated (closed vs open), what layer or unit behavior applies, or what side effects occur.

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 efficient and readable, though its brevity reflects the overall lack of detail rather than an optimal balance for a four-parameter creation tool.

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

Completeness2/5

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

Given four parameters, no annotations, no output schema, and 0% schema description coverage, the description is too sparse. It omits sibling differentiation, unit/layer handling, profile validation rules, and any expectation for the returned entity.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It explains profile_id and height by mapping them to '2D profile entity' and 'height', but the optional 'unit' and 'layer' parameters receive no explanation beyond the enum values already present in the schema.

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 a prism') and identifies the required inputs (2D profile entity and height). It clearly separates this from primitive creators like create_box or create_sphere, though it does not explicitly compare itself to profile-based siblings like sweep or create_revolution.

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 create_box, sweep, or create_revolution. It implies usage only by stating the required inputs, leaving the agent to infer the appropriate context.

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