Skip to main content
Glama
Sign In
CDT AutoCAD Provider

CDT AutoCAD Provider

by SlncTrZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

layer_set_current

Sets an existing layer as the active document layer so new entities are created on it; existing objects remain unchanged.

Instructions

Set an existing layer as the active document layer; this changes session drawing state but does not move existing objects between layers.

Side-effects: Changes current working layer for subsequent entity creation. Disambiguation: Does not modify existing entities; only sets active context.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "layer_set_current"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of existing layer to set as current active layer

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • addedInput schema / properties / name / description
      Added value: +"Name of existing layer to set as current active layer"
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With only readOnlyHint=false available, the description carries real weight: it discloses the side-effect (changes the working layer for subsequent entity creation), clarifies that existing objects are not re-assigned, and labels it as session drawing state. It stops short of saying whether the setting persists on save or is undoable, which would be the remaining behavioral detail.

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?

Three short, labeled sentences, front-loaded with the core action, then side-effects, then disambiguation. No sentence is redundant or restates the tool name.

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?

One required parameter, an output schema, and a minimal annotation set — the description supplies exactly the missing pieces (state change scope, non-mutation of geometry) without needing to explain return values. Nothing an agent needs to invoke it correctly is absent.

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% and the single parameter is fully documented in the schema, so the baseline applies. The description reinforces the 'existing layer' constraint (implying an error if the name is unknown) but adds no format or resolution details 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?

States a specific verb and resource ('Set an existing layer as the active document layer') and immediately scopes it ('existing layer', not creation). An agent can distinguish it from layer_create and layer_update_state without opening any schema.

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?

The Disambiguation section makes explicit what the tool does not do (does not modify existing entities, only sets active context), which prevents misuse after a layer rename or property change. It does not name sibling tools such as layer_create or layer_update_state as alternatives, so routing is inferred rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools