Skip to main content
Glama
BricsCAD MCP

BricsCAD MCP

by alesdev88

bricscad_list_blocks

Read-only

Lists block definitions with insert counts, including nested and dynamic blocks, for auditing drawings. Use include_anonymous to also list anonymous blocks holding dynamic block states.

Instructions

List block definitions with insert counts, including nested inserts and inserts of dynamic blocks. Up to 2000 per call.

include_anonymous: also list the anonymous blocks, such as *U12, that hold a dynamic block's states.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
timeoutNo
include_anonymousNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description still adds real value with the 'Up to 2000 per call' ceiling and the note that anonymous blocks back dynamic block states, but it says nothing about pagination behavior, whether the cap overrides the limit parameter, or per-drawing scoping.

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?

Two tight sentences, front-loaded with the core capability and followed by the one flag that needs explanation. The flag is named inline rather than in a separate param block, which is acceptable but slightly awkward against the newline.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 annotations handle the safety profile. For a paged listing tool with four undocumented parameters, however, the description leaves pagination semantics (how limit 200 relates to the 2000 ceiling, what offset counts) unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must explain all four parameters. It fully explains only include_anonymous; limit, offset, and timeout get no semantic treatment, and 'Up to 2000 per call' arguably conflicts with the limit default of 200 without clarifying whether 2000 is a hard cap.

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 block definitions') plus meaningful scope: insert counts, nested inserts, and dynamic-block inserts. That scope distinguishes it from the other list_* siblings (layers, layouts, xrefs) by resource alone, though it never names an alternative 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 include_anonymous sentence implies when to turn that option on (you want the *U12-style blocks that back dynamic block states), which is genuine usage guidance for one flag. There is no overall statement of when to call this versus other listing tools, no prerequisites, and no exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.