Skip to main content
Glama
BricsCAD MCP

BricsCAD MCP

by alesdev88

bricscad_read_attributes

Read-only

Read attribute values from BricsCAD block inserts, such as title block contents, using wildcard block names and layout filters to audit drawings.

Instructions

Read attribute values from block inserts, for example title block contents. Up to 2000 per call.

block: a block name, which may use the wildcards * and ?. A dynamic block goes by its own name. layout: "Model" or a layout name.

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

Input Schema

NameRequiredDescriptionDefault
blockNo
limitNo
layoutNo
offsetNo
timeoutNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior4/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, and the description adds genuinely new behavioral context: a 2000-per-call cap, wildcard matching on block names, and the fact that dynamic blocks are addressed by their own name rather than the parent definition. Remaining gaps such as what happens when a block has no attributes are minor.

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 the core purpose in the first clause, followed by a compact per-parameter glossary with no filler. The 'layout' line reads slightly as a fragment and the page cap is buried at the end of the first sentence rather than near 'limit'.

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 shape need not be explained, and the read-only annotations remove the need for destructive-behavior warnings. Still, for a 5-parameter tool with zero schema descriptions, the definition leaves offset (paging) and timeout behavior unexplained, which an agent needs to paginate past the 2000 cap.

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 0% across 5 parameters, so the description carries the full burden; it explains 'block' (wildcards, dynamic block naming) and 'layout' ("Model" or a layout name) usefully, and 'Up to 2000 per call' hints at the limit parameter's ceiling. However 'offset' and 'timeout' are never mentioned, leaving two parameters with no semantics anywhere.

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?

The description gives a specific verb and resource ('Read attribute values from block inserts') plus a concrete example ('title block contents'), which is enough for an agent to know exactly what is returned. It does not explicitly distinguish itself from the sibling bricscad_set_attributes, though the read/write split is obvious from the names, so it falls short of a 5.

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 by the example ('title block contents'), which tells the agent a typical scenario, but there is no explicit when-to-use/when-not-to-use statement and no pointer to an alternative such as bricscad_list_blocks for discovering block names before calling this. The agent must infer the workflow.

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