Skip to main content
Glama
danielproxd2

MCP_CAD

by danielproxd2

run_batch_job

Execute a recorded batch job file by file, producing a complete manifest with counts for changed, skipped, inspected, and failed items. Read-only actions are logged as inspected. No files are deleted.

Instructions

Ejecuta un BatchJob registrado: aplica el verbo archivo POR archivo, con recibo por archivo (abierto/op/guardado/cerrado) y un MANIFIESTO COMPLETO — cada archivo saltado se reporta (truncar en silencio es el pecado capital).

ESTA llamada (aprobada en el cliente MCP) es la aprobación humana del lote.

Compuertas (tres niveles, como run_assembly_plan):

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

  2. advertencias 'risky' (irreversible-sin-guardar / ruta de red) bloquean salvo override_warnings=True (flag INDEPENDIENTE — forzar una no desactiva la otra);

  3. fileset vacío o '' sin resolver → se RECHAZA SIEMPRE. No borra archivos (borrado diferido por diseño). Devuelve {ok, changed, skipped, inspected, failed, manifest, failures, log_path} (los verbos de solo-lectura — rebuild/interference/BOM — cuentan como 'inspected', no 'skipped'). [en: Execute a recorded batch job file by file; complete manifest, every skip reported; read-only verbs counted as 'inspected'; no deletion.]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
batch_job_idYes
override_warningsNo
override_low_confidenceNo
Behavior4/5

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

With no annotations, the description carries full burden. It discloses no deletion, read-only verbs counted as 'inspected', and details three safety gates. It lacks explicit statement about mutability but implies writing actions.

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, bilingual (Spanish and English redundant), and uses bullet-like structure. It could be more concise without repeating information in both languages.

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

Completeness4/5

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

Given no output schema, the description covers return fields, gates, and verb counting. However, it lacks detail on batch_job_id format and full return types, leaving some gaps.

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

Parameters3/5

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

Schema coverage is 0%. The description explains override_warnings and override_low_confidence in the gates, but batch_job_id is only implicitly identified as the job to run, with no format or source details.

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 it executes a recorded batch job file by file with a complete manifest, and distinguishes from siblings by referencing run_assembly_plan and noting it is the human approval step.

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?

It describes when to use (after recording a batch job, as human approval) and conditions that block execution (go_recommendation, warnings, empty fileset). However, it does not explicitly list alternatives or when not to use.

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