Skip to main content
Glama
Sign In
CDT AutoCAD Provider

CDT AutoCAD Provider

by SlncTrZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

layout_create

Creates a new blank paper-space layout by name, rejecting duplicate or empty names while preserving existing layouts. Add viewports separately after creation.

Instructions

Create a new paper-space layout by name; duplicate or empty names are refused and existing layouts are preserved.

Side-effects: Adds layout to drawing. Disambiguation: Creates blank sheet; viewports must be added separately with viewport_create.

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_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName for the new paper-space layout sheet

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 for the new paper-space layout sheet"
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, so the description carries real weight: it discloses the side effect ('Adds layout to drawing'), the failure mode for duplicate/empty names, and the guarantee that existing layouts are preserved. It doesn't state what is returned or whether the new layout becomes current.

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 lines, zero filler, and the core creation statement plus name constraint are front-loaded before the side-effect and disambiguation notes.

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 an output schema present and only one parameter, the description covers purpose, side effect, refusal behavior, and next step. The one notable omission for an agent is whether the newly created layout becomes the current layout, given the existence of layout_set_current.

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 coverage is 100% with a single documented parameter, so the baseline is 3; the description adds meaningful constraint semantics ('duplicate or empty names are refused') that the schema does not express, which justifies the bump.

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 gives a specific verb plus resource ('Create a new paper-space layout by name') and explicitly contrasts the tool with viewport_create, so the agent can distinguish it from siblings 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?

It names the alternative explicitly ('viewports must be added separately with viewport_create') and states the when-not condition (duplicate or empty names are refused). It doesn't discuss how this relates to layout_set_current or when a caller would pick an existing layout instead, so it falls short of full 5-level guidance.

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