Skip to main content
Glama
Sign In
CDT AutoCAD Provider

CDT AutoCAD Provider

by SlncTrZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

layout_set_current

Switches the active drawing to an existing layout, such as Model or Layout1, changing the current model/paper-space context for subsequent operations.

Instructions

Switch the active document to an existing layout; this changes the operator's current model/paper-space context.

Side-effects: Changes operator active space context. Disambiguation: Switch between Model and paper layouts.

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": "layout_set_current"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of existing layout to activate (e.g. 'Model' or 'Layout1')

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 layout to activate (e.g. 'Model' or 'Layout1')"
  2. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only state readOnlyHint=false, indicating a mutation. The description adds meaningful context by disclosing the side-effect: changing the operator's active space context. It does not cover failure behavior for invalid layout names, but the key behavioral impact is disclosed.

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 appropriately sized and front-loads the action. However, it repeats the same idea twice: 'changes the operator's current model/paper-space context' and 'Changes operator active space context.' That redundancy slightly weakens efficiency.

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 the mutation annotation, single required parameter, output schema, and clear side-effect disclosure, the description is nearly complete for an agent to call it correctly. Only minor gaps remain, such as failure handling when the named layout does not exist.

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 description coverage is 100%, with the single 'name' parameter already documented and exemplified in the schema. The description adds no additional parameter meaning beyond what the schema provides, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: switching the active document to an existing layout. It clearly distinguishes this from creating layouts by saying 'existing layout' and clarifies the model/paper-space context. It stops short of naming sibling tools like layout_list or layout_create, so a 4 rather than a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'Switch between Model and paper layouts' implies when to use the tool, and 'existing layout' implicitly excludes creation. However, it does not explicitly state when not to use it or name layout_list/layout_create as alternatives, leaving usage guidance to inference.

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