Skip to main content
Glama
BricsCAD MCP

BricsCAD MCP

by alesdev88

bricscad_list_layouts

Read-only

Lists Model and paper space layouts with their entity counts to audit BricsCAD drawings, returning up to 2,000 per call with offset and limit pagination.

Instructions

List Model and the paper space layouts with their entity counts. Up to 2000 per call.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
timeoutNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.8/5.0
Behavior2/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 adds one genuine behavioral fact — a 2000-per-call ceiling — but says nothing about pagination behavior, how offset interacts with that cap, whether 'entity counts' include nested block entities, or what happens on timeout, and the 2000 cap is not reconciled with the schema's default limit of 200.

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 short sentences with zero filler, and the resource being listed is front-loaded. The qualifier 'Up to 2000 per call' is slightly ambiguous about whether it refers to the limit parameter or an internal truncation, which keeps it from a 5.

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-value structure needn't be explained. However, for a paginated tool with three undocumented parameters and no stated prerequisites, an agent still lacks enough to page correctly or set a sensible timeout.

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 all three parameters (limit, offset, timeout) carry no meaning in the schema. The description only sheds light on one of them via the 'up to 2000 per call' cap; offset paging and the timeout parameter are entirely undocumented, leaving most of the parameter surface unexplained.

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 ('List') and resource ('Model and the paper space layouts') plus the enrichment returned ('their entity counts'). The sibling list tools target different resources (blocks, layers, xrefs), so the resource noun alone differentiates it, though the description never acknowledges any sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites (e.g. whether a drawing must be open), and no mention of alternatives such as bricscad_drawing_info or bricscad_query_entities for entity-level inspection. Usage is only inferable from the verb.

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