Skip to main content
Glama
CaeliaEve

AutoCAD MCP Ultra

by CaeliaEve

Batch Modify Entities

entity_batch_modify

Apply multiple CAD entity modifications in one call, including move, rotate, scale, delete, and property updates. Group operations to reduce round-trips and process batches efficiently.

Instructions

Apply multiple modifications in a single call.

Example: [{"handle": "1A", "action": "move", "dx": 10, "dy": 20}, {"handle": "2B", "action": "delete"}]

Covers move/rotate/scale/delete/set_properties only. For anything else, for ordering, or to feed one step's result into the next, use cad_batch.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationsYesList of operations. Each dict: {handle, action, ...params}. Actions: move(dx,dy), rotate(base_x,base_y,angle_deg), scale(base_x,base_y,factor), delete, set_properties(layer,color,...)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

注解仅提供readOnlyHint=false,没有破坏性提示。描述没有明确说明这是修改操作的影响(如是否可逆、对原图的影响),但也没有与注解矛盾。示例和操作列表提供了基本行为预期,但缺少对副作用或事务性的深入说明。

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?

描述结构紧凑:先说明核心功能,再用示例演示,最后给出边界条件和替代工具指引。每句话都有信息量,但示例占用了部分空间,略可精简。

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?

该工具只有一个参数且schema已完整覆盖,描述提供了操作类型和界线,足以让代理正确调用。但与cad_batch的区分已明确,整体对于简单批量修改场景已足够。缺少的仅是更深入的行为副作用或失败模式说明,这属于轻微不足。

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对operations参数的描述覆盖率为100%,但描述中提供的操作含义(dx/dy、base_x/base_y/angle_deg、factor等)和示例补充了schema未详细说明的参数格式,帮助代理正确构造操作字典。

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?

描述以具体动词'Apply multiple modifications in a single call'开头,明确了资源和批量操作的核心目的。示例进一步澄清了输入格式,而'Covers move/rotate/scale/delete/set_properties only'清晰界定了范围,足以与cad_batch等兄弟工具区分。

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?

描述明确说明了支持的操作集合,并直接指出对于其他操作、需要排序或需要步骤间依赖的场景应使用cad_batch。这为代理提供了清晰的何时用此工具以及何时转向替代方案的条件。

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/CaeliaEve/autocad-mcp-ultra'

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