Skip to main content
Glama

cad_batch

Destructive

Run, schedule, and manage sequences of CAD operations as batch jobs. Supports synchronous execution, cron/one-off scheduling, dependency chaining, sandboxed scripts, and job inspection.

Instructions

Execute, schedule, inspect or manage batch jobs.

按 ``action`` 执行批处理操作:execute / schedule / status / cancel / list /
templates / run_script。
- ``execute``: run a list of tool calls synchronously (each ``command``
  has ``tool`` + ``arguments``); ``stop_on_error`` halts on the first
  failure.
- ``schedule`` / ``status`` / ``cancel`` / ``list``: create and manage
  one-off / cron / dependency-chained jobs (durable across restarts).
- ``templates``: list reusable Jinja2 command templates.
- ``run_script``: execute a sandboxed script (python / scr / batch).

When not to use: ``cad_batch`` sequences *other* tools. For a single
operation call the concrete aggregate directly (``cad_object``,
``cad_file``, ...). ``execute`` is synchronous — use ``schedule`` for
long-running work.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
batchNoBatch action to perform, discriminated by `action`: execute (run commands synchronously), schedule, status, cancel, list, templates or run_script.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okNoWhether a script completed successfully
jobsNoJob summaries
nameNoJob name
stateNoJob state
actionYesBatch action
job_idNoJob id
statusYesOperation status
stderrNoCaptured stderr
stdoutNoCaptured stdout
messageNoStatus description
resultsNoPer-command results
exit_codeNoProcess exit code
templatesNoTemplate names
timed_outNoWhether execution hit the timeout
created_atNoCreation timestamp
duration_msNoExecution time in milliseconds
script_typeNoScript type that ran
failed_countNoFailed commands
command_countNoNumber of commands
success_countNoSuccessful commands
blocked_importsNoBlocked imports
Behavior5/5

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

The description adds substantial behavioral context beyond the annotations: execute is synchronous, scheduled jobs are 'durable across restarts', run_script is 'sandboxed', and stop_on_error halts on first failure. It also explains that schedule supports cron/dependency-chained jobs. This complements the destructiveHint annotation without contradicting it.

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

Conciseness5/5

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

The description is well-structured with bullets, a clear action list, and a dedicated 'When not to use' section. Despite covering seven actions, it remains scannable and every sentence adds relevant information without fluff. The bilingual text is a minor stylistic note but does not hurt clarity.

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 tool's complexity (seven actions, scheduling, templating, scripts), the description covers all key aspects: action semantics, synchronous vs scheduled execution, durability, sandboxing, and guidance for alternatives. With an output schema available, returning to documentation is unnecessary. The description is sufficiently complete for safe and correct invocation.

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?

The input schema has 100% coverage and a well-defined discriminated union, so the baseline is 3. The description adds value by clarifying the semantics of each action (e.g., execute runs tool+argument pairs, run_script is sandboxed, schedule supports cron/dependencies). It helps the agent understand how to choose the 'batch' union variant, which exceeds schema-only information.

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 purpose with a specific verb set ('Execute, schedule, inspect or manage batch jobs') and then enumerates each action (execute, schedule, status, cancel, list, templates, run_script). It distinguishes itself from sibling CAD tools by explicitly noting that it sequences other tools, making the purpose unambiguous.

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?

The description provides explicit usage guidance including a 'When not to use' section: 'For a single operation call the concrete aggregate directly (cad_object, cad_file, ...)' and distinguishes synchronous execute from scheduled long-running work. This directly tells the agent when to prefer alternatives and when to use this tool.

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/Tianshang301/TianshangCAD'

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