Skip to main content
Glama
Sign In
MCP_CAD

MCP_CAD

by danielproxd2
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

build_extruded_closed_profile

Constructs an exact closed profile from segment coordinates and extrudes it as a single composite body. Supports variables for parametric depth and dimensions.

Instructions

Build an exact closed profile and extrude it as one composite.

Segment coordinates and depth_mm accept string expressions over variables (e.g. depth_mm="C", x2="A-29") — a size variant is the same call with a new variables dict.

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": {
      "segments": "<segments>",
      "depth_mm": "<depth_mm>"
    },
    "name": "build_extruded_closed_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
exactNo
mergeNo
planeNofront
depth_mmYes
segmentsYes
variablesNo
end_conditionNoblind
reverse_directionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It discloses the parametric expression capability, but lacks details on side effects (e.g., does it merge automatically? What if the profile is not closed?), error behavior, or prerequisites. Essential behavioral traits are omitted.

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 concise (two sentences) and front-loaded with purpose. However, it lacks structural formatting (e.g., bullet points) that could improve readability, especially for a parameter-heavy 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 the tool's complexity (8 params, no output schema, no annotations), the description is incomplete. It explains only the variable expression aspect, leaving out parameter semantics, output details, and workflow integration. A more complete description would address the purpose of each parameter and the expected result.

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 description must compensate. It adds meaning for 'segments' and 'depth_mm' (accept expressions over variables), but ignores the other six parameters (exact, merge, plane, end_condition, reverse_direction, variables). The description is insufficient for an 8-parameter tool.

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?

The description clearly states the tool's action: 'Build an exact closed profile and extrude it as one composite.' It uses specific verbs and resources, and distinguishes from siblings like 'build_closed_profile' which only builds, and 'extrude_sketch' which extrudes an existing sketch.

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?

The description implies usage for parametric designs by mentioning string expressions over variables, but does not explicitly state when to use this tool versus alternatives (e.g., building a closed profile then extruding separately). No when-not or exclusion criteria are provided.

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