Skip to main content
Glama
Sign In
CDT AutoCAD Provider

CDT AutoCAD Provider

by SlncTrZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

object_list

Read-only

List drawing objects from the current space with optional type and layer filters plus pagination, returning backend object IDs for sequential browsing. Use object_query for spatial filtering.

Instructions

List objects from the backend's current supported space with optional type/layer filters and bounded pagination; returned IDs are backend object identifiers.

Side-effects: None. Read-only entity query. Disambiguation: Use for sequential browsing of objects; use object_query when spatial filtering or bounding box measurements are needed.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of objects to return per page (default: 200)
offsetNoStarting index offset for pagination (default: 0)
type_filterNoOptional entity type filter (e.g. 'LINE', 'CIRCLE', 'LWPOLYLINE', 'INSERT')
layer_filterNoOptional layer name filter

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.1
    • addedInput schema / properties / layer_filter / description
      Added value: +"Optional layer name filter"
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of objects to return per page (default: 200)"
    • addedInput schema / properties / offset / description
      Added value: +"Starting index offset for pagination (default: 0)"
    • addedInput schema / properties / type_filter / description
      Added value: +"Optional entity type filter (e.g. 'LINE', 'CIRCLE', 'LWPOLYLINE', 'INSERT')"
  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?

Annotations already carry readOnlyHint=true, so 'Side-effects: None. Read-only entity query.' largely restates structured data, but the description adds real value beyond that: results are bounded by pagination and the returned IDs are backend identifiers rather than drawing handles. That ID-semantics note is context an agent cannot get from annotations or the schema.

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?

Front-loaded with purpose, then three short labeled clauses; nothing is buried. The 'Side-effects: None' line is slightly redundant with the annotation, but it is compact and does not distract.

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-value explanation is not required. Scope, safety, pagination bounding, ID semantics, and sibling routing are all covered. Minor gap: no indication of result ordering or that zero filters returns the entire space, which matters for a default-200-paginated listing tool.

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 limit/offset defaults and example entity types already documented per-property. The description only gestures at 'type/layer filters and bounded pagination' without adding format or interaction detail (e.g. whether filters combine, what bound applies). Baseline 3 is appropriate.

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 ('List objects from the backend's current supported space') plus the filter and pagination scope, and explicitly names the sibling it is not (object_query). An agent can distinguish it from object_get, object_count, and object_query without opening a schema.

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?

Gives an explicit positive selection rule ('use for sequential browsing') and the exact condition that should route the agent elsewhere ('use object_query when spatial filtering or bounding box measurements are needed'). Alternatives and exclusions are both named.

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