Skip to main content
Glama
danielproxd2

MCP_CAD

by danielproxd2

run_macro_job

Execute a recorded macro job by materializing VBA to a temp .swb, running it, and rebuilding. Safety gates block network egress and require override for warnings.

Instructions

Execute a recorded MacroJob by materializing VBA to a temporary .swb.

Disabled by default. Set MCP_CAD_ENABLE_UNSAFE_MACROS=1 before starting the server to opt in. This is arbitrary code execution; heuristic token scans, source review, warning overrides, audit logging, and temporary-file cleanup do not sandbox the macro or prove that it is safe.

Ejecuta un MacroJob registrado: materializa la fuente en un .swb temporal EN EL HOST, lo corre vía RunMacro2 (UserControl=False), reconstruye y borra el temporal. Ejecuta VBA arbitraria (cruza la restricción #2). ESTA llamada (aprobada en el cliente MCP) es la aprobación humana.

Compuertas (cuatro niveles): 0) señales de EGRESO a la red (HTTP/stream/descarga/UNC) → restricción #1, RECHAZO NO ANULABLE (la geometría no sale del host — #1 no está waived, a diferencia de #2);

  1. go_recommendation='partial_or_handback' bloquea salvo override_low_confidence=True;

  2. advertencias 'risky' (siempre incluyen la nota de #2; más señales de sistema de archivos/shell) bloquean salvo override_warnings=True (flag independiente);

  3. '' sin resolver en el código → se RECHAZA SIEMPRE. La fuente que corre se anexa a un log de auditoría en el host (MCP_CAD_MACRO_AUDIT_LOG). El .swb nunca sale del host (VBA es texto). Devuelve {ok, ran, run_error, rebuilt, audit_log, audit_recorded}. [en: Execute a recorded macro job — temp .swb on-host, RunMacro2, rebuild, delete temp; network-egress is a hard non-overridable block (constraint #1); source appended to the on-host audit log.]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
macro_job_idYes
override_warningsNo
override_low_confidenceNo
Behavior5/5

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

Since no annotations are provided, the description carries the full burden. It discloses arbitrary code execution, network egress block, audit logging, temporary file cleanup, and four levels of gates with clear conditions. Returns are listed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is verbose, mixing English and Spanish, and contains redundant translations. While organized with bullet points, it could be more concise to improve readability.

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?

Given the complexity and no output schema, the description fully explains the tool's behavior, safety considerations, return values, and prerequisites. No gaps identified.

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

Parameters4/5

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

Schema description coverage is 0%, but the description explains override_warnings and override_low_confidence in the gates context. macro_job_id is not elaborated, but its purpose is implied. Adds value beyond parameter names.

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 'Execute a recorded MacroJob by materializing VBA to a temporary .swb,' specifying the verb and resource. It distinguishes from siblings like run_batch_job and run_assembly_plan by focusing on macros.

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

Usage Guidelines4/5

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

Explicitly states it is disabled by default and requires opt-in (MCP_CAD_ENABLE_UNSAFE_MACROS=1). Details the four gates and when overrides are allowed, providing clear context for usage. Does not explicitly compare to alternatives but implies caution.

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