Skip to main content
Glama
danielproxd2

MCP_CAD

by danielproxd2

run_feature_plan

Execute a precompiled FeaturePlan to build the model in a single batch, with automated verification after construction. Supports manual override for low-confidence plans or unmodeled internal features.

Instructions

Construye un FeaturePlan compilado en UNA sola pasada (compila una vez, construye una vez).

Flujo recomendado para dibujos/PDF:

  1. record_drawing_spec → fija la lectura.

  2. compile_feature_plan_from_drawing_spec → obtén el plan y MUÉSTRASELO al diseñador (pasos, dimensiones, advertencias).

  3. run_feature_plan(feature_plan_id) → ESTA llamada (aprobada en el cliente MCP) es la aprobación humana del build completo; ejecuta todos los pasos que mutan el modelo dentro de UN solo lote (redibujo/reconstrucción diferidos a una sola reconstrucción al final).

  4. revisa el verify_build_report devuelto + el render final.

[en: Build a compiled FeaturePlan in ONE pass. Show the plan to the designer after compiling; calling this tool (approved in the MCP client) is the single human-in-the-loop approval of the whole build. Mutating steps run inside one batch scope; verification runs once at the end.]

Compuerta de confianza: un plan marcado para "partial_or_handback" NO se construye solo — pasa override_low_confidence=True para forzarlo tras revisar las advertencias. Un plan con dimensiones sin resolver () se rechaza siempre: nunca se inventa una cota.

Compuerta de features internas: si el spec registró barrenos/ranuras punteadas que el plan NO modela (unmodeled_internal_features), se bloquea — pasa override_unmodeled_internal=True para construir sin ellas (flag independiente de override_low_confidence: forzar una no desactiva la otra).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
feature_plan_idYes
override_low_confidenceNo
override_unmodeled_internalNo
Behavior5/5

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

With no annotations, description fully discloses behavior: it runs mutating steps in one batch, verifies once at end, acts as human-in-the-loop approval. Guard conditions (low confidence, unmodeled internal, unresolved dimensions) are explained, as is the return of verify_build_report and final render.

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?

Dense with information and well-structured with workflow and conditions. However, the English translation duplicates the Spanish content; removing the translation would make it more concise without loss. Still, every sentence adds value and the structure is logical.

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?

Covers purpose, workflow, guard conditions, parameter semantics, and return value (verify_build_report + render). Despite no output schema, the description provides sufficient context for an agent to use the tool 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?

Despite 0% schema description coverage, the description explains all three parameters: feature_plan_id (implicitly from compilation), override_low_confidence (for forcing partial plans), and override_unmodeled_internal (for missing internal features). States independence of the two boolean overrides.

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?

Description clearly states the tool builds a compiled FeaturePlan in one pass. It distinguishes from sibling compile_feature_plan_from_drawing_spec by being the execution/approval step. The workflow steps explicitly position this tool as the final build step.

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

Usage Guidelines5/5

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

Provides a recommended 4-step workflow with clear context for when to use this tool. Explicitly states when not to use: plans with partial_or_handback or unmodeled internal features require overrides. Unresolved dimensions are blocked entirely.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/danielproxd2/solidworks-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server