Skip to main content
Glama
Sign In
CDT AutoCAD Provider

CDT AutoCAD Provider

by SlncTrZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

viewport_list

Read-only

Lists paper-space viewports for a specific layout or all layouts, returning handles, geometry, scale, lock state, and ownership hints for read-only inspection.

Instructions

List paper-space viewports for one or all layouts with handle, geometry, target, scale, lock state, and backend-created ownership hint.

Side-effects: None. Read-only viewport query. Disambiguation: Inspect viewport handles, scales, and bounding boxes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
layoutNoOptional layout name filter. Lists viewports across all layouts if omitted

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • addedInput schema / properties / layout / description
      Added value: +"Optional layout name filter. Lists viewports across all layouts if omitted"
  2. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

readOnlyHint=true already declares the safety profile, and "Side-effects: None. Read-only viewport query." merely repeats it rather than adding context. The one piece of added value is the note that results carry a "backend-created ownership hint," which signals what the agent will see, but no pagination, error, or size behavior 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?

Three short labeled lines with the core action front-loaded and no filler prose. The "Side-effects" line duplicates the annotation and partly duplicates "Read-only viewport query," which is mild waste but not bloat.

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?

An output schema exists, so return values needn't be explained, and the description still names the key fields. With one optional parameter and a read-only operation, nothing essential for correct invocation is missing; only edge-case behavior is unaddressed.

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% and the single param is fully documented in the schema, so baseline 3 applies. The phrase "for one or all layouts" mirrors the schema's own note that omitting the filter lists across all layouts, adding no new semantics.

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?

States a specific verb and resource ("List paper-space viewports") with the scope "one or all layouts" and enumerates the returned fields (handle, geometry, target, scale, lock state). The verb 'list' clearly separates it from viewport_create, viewport_set_scale, viewport_lock, and viewport_delete siblings, though no sibling is named explicitly.

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 "Disambiguation" line ("Inspect viewport handles, scales, and bounding boxes") restates the purpose rather than giving when-to-use versus when-to-use-an-alternative guidance. The optional layout filter implies usage context, but there are no explicit exclusions or named alternatives.

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