Skip to main content
Glama

cad_layer

Destructive

Create, read, update, delete, or list CAD layers to organize objects for display and selection. Adjust visibility, locking, color, linetype, and linewidth.

Instructions

Create, read, update, delete or list layers.

聚合图层操作。按 ``action`` 派发:create / read / update / delete / list。
Layers group objects for display and selection. ``create`` accepts
color / linetype / linewidth; ``update`` can also toggle ``visible`` /
``locked``; ``delete`` removes the layer *and* the objects on it.

When not to use: for per-object layer membership use ``cad_object``
(create/update with a ``layer``); for per-layer object counts use
``cad_status`` (target=layer). To hide objects without deleting them
prefer ``cad_layer`` (update visible=false).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
layerYesLayer action to perform, discriminated by `action`: create, read, update, delete or list.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoLayer name
colorNoLayer color
actionYesLayer action executed
layersNoLayer definitions
lockedNoLock state
statusYesOperation status
messageNoStatus description
visibleNoVisibility
linetypeNoLine type
linewidthNoLine width
Behavior4/5

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

Annotations already declare destructiveHint=true, so the description adds value by specifying that 'delete removes the layer *and* the objects on it'—a critical side effect. It also explains the layer concept (grouping objects for display/selection) and that update can toggle visibility/locked, going beyond the generic destructive flag.

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?

The description is front-loaded with the purpose and well-structured, ending with explicit alternatives. The Chinese sentence duplicates the English dispatch explanation, adding minor redundancy, but the overall length is appropriate and every sentence contributes useful context.

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?

With a rich union schema and an output schema present, the description covers the CRUD operations, critical destructive behavior, and alternatives. It lacks details on error conditions or return formats, but those are not required given the output schema and the tool's straightforward nature.

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 100%, so the baseline is 3. The description summarizes what each action accepts (e.g., create accepts color/linetype/linewidth; update can toggle visible/locked), but these details are already present in the schema's property descriptions. It does not add new format or syntax information beyond the 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?

The description opens with 'Create, read, update, delete or list layers,' a specific verb+resource combination. It further distinguishes from siblings by explicitly naming cad_object and cad_status as alternatives for different use cases, making the tool's scope unmistakable.

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 'When not to use' section gives explicit alternatives: per-object layer membership via cad_object, per-layer object counts via cad_status, and hiding objects via cad_layer (update visible=false). This provides clear decision guidance for when to use this tool versus siblings.

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