Skip to main content
Glama
Sign In
CDT AutoCAD Provider

CDT AutoCAD Provider

by SlncTrZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

block_list

Read-only

List named block definitions, excluding anonymous blocks, with base point, entity count, attribute count, and xref status to discover available blocks before insertion.

Instructions

List named block definitions, excluding anonymous blocks, with base point, entity count, attribute-definition count, and xref status.

Side-effects: None. Read-only block definition query. Disambiguation: Use to discover available blocks before inserting.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum block definitions to return (default: 200)
offsetNoPagination offset index (default: 0)
name_filterNoOptional substring filter on block name
include_xrefsNoWhether to include external reference blocks (default: True)
include_xref_dependentNoWhether to include XREF-dependent blocks (default: False)

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.1.1
    • addedInput schema / properties / include_xref_dependent
      Added value: +{
+  "default": false,
+  "description": "Whether to include XREF-dependent blocks (default: False)",
+  "type": "boolean"
+}
    • addedInput schema / properties / include_xrefs
      Added value: +{
+  "default": true,
+  "description": "Whether to include external reference blocks (default: True)",
+  "type": "boolean"
+}
    • addedInput schema / properties / limit
      Added value: +{
+  "default": 200,
+  "description": "Maximum block definitions to return (default: 200)",
+  "type": "integer"
+}
    • addedInput schema / properties / name_filter
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional substring filter on block name"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "description": "Pagination offset index (default: 0)",
+  "type": "integer"
+}
  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?

The description reinforces the read-only annotation by stating 'Side-effects: None' and adds useful scope behavior by excluding anonymous blocks. It does not elaborate on pagination or performance, but with readOnlyHint already covering safety, the added behavioral context is solid.

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?

The description is front-loaded with the core operation, then efficiently adds side-effect and disambiguation notes. Every sentence contributes useful information without repetition.

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?

For a read-only list tool with full schema coverage, readOnlyHint, and an output schema, the description covers purpose, scope, side effects, and usage context. Nothing critical is missing for correct invocation.

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%, so the schema already documents limit, offset, name_filter, include_xrefs, and include_xref_dependent. The description does not add parameter-level detail beyond the schema, which is the expected baseline when the schema does the heavy lifting.

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 uses a specific verb and resource: list named block definitions, excluding anonymous blocks. It also states the returned fields, so an agent can distinguish this from block creation/insertion and xref-specific tools.

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 gives a clear usage context: discover available blocks before inserting. It does not explicitly name alternatives or when-not-to-use cases, but the guidance is sufficient for routing relative to block_insert and batch_insert_blocks.

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