Skip to main content
Glama
BricsCAD MCP

BricsCAD MCP

by alesdev88

bricscad_list_layers

Read-only

List drawing layers with visibility, frozen and locked state, color, linetype and entity count, paged up to 2000 per call. Use it to audit layer setup and usage.

Instructions

List layers with their on, frozen and locked state, color, linetype and entity count. 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_layers"
  }
}

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

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 the safety profile is covered. The description adds one genuinely new behavioral fact, the 2000-per-call cap, but says nothing about ordering, whether a drawing must be open, or what happens past the cap.

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 dense sentences, front-loaded with the return fields, with no filler. The cap sentence is slightly ambiguous, since it is unclear whether 2000 is the maximum accepted limit value or the maximum rows returned.

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 the field list need not be re-explained and completeness is judged mainly on operability. For a simple read tool that is adequate, but the paging contract (how limit, offset and the 2000 cap interact) is the one thing an agent actually needs and it is absent.

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% for three parameters (limit default 200, offset default 0, timeout default 30 seconds). The description only indirectly touches limit via the 2000 ceiling and leaves offset paging and timeout meaning entirely undocumented, so it does not compensate for the coverage gap.

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 layers") and enumerates exactly what each entry contains: on/frozen/locked state, color, linetype, entity count. This is clearly distinct from the sibling mutator bricscad_set_layer by name and verb, though the description itself never names an alternative.

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?

Usage is implied rather than stated: an agent can infer this is the inspection tool for layer state, and the "Up to 2000 per call" note hints that large layer sets need paging. There is no explicit when-to-use, no when-not, and no advice on paging with limit/offset.

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