Skip to main content
Glama
BricsCAD MCP

BricsCAD MCP

by alesdev88

bricscad_find_text

Read-only

Searches literal text across TEXT, MTEXT, MULTILEADER, table cells, and block attributes, returning matches with handles and positions.

Instructions

Search TEXT, MTEXT, MULTILEADER, table cell and block attribute text for literal text.

A table cell comes back with its table's handle and position, plus its row and column. Up to 2000 per call.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "bricscad_find_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
offsetNo
timeoutNo
case_sensitiveNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/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 adds genuine behavior in explaining that table-cell hits return the parent table's handle and position plus row/column. However, 'Up to 2000 per call' sits in tension with a `limit` parameter defaulting to 200 and is never reconciled, leaving the actual result-cap semantics unclear.

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?

Three short sentences, scope front-loaded and no filler. The trailing fragment 'Up to 2000 per call.' is terse to the point of ambiguity, which slightly undercuts the otherwise tight structure.

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

Completeness2/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 shapes need not be explained, and the table-cell special case is a nice addition. But for a tool with five undocumented parameters at 0% schema coverage and a sibling set full of overlapping query tools, the description omits pagination behavior, case matching, and timeout semantics that an agent needs to call it correctly.

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% across five parameters, so the description carries the full burden and largely fails: `case_sensitive`, `offset`, and `timeout` are never mentioned, and `query` is only obliquely implied by 'literal text'. The single hint given ('Up to 2000 per call') is ambiguous about whether it bounds `limit` or the whole call.

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 ('Search') and enumerates the exact resource types covered (TEXT, MTEXT, MULTILEADER, table cells, block attributes), which tells an agent precisely what is in scope. It does not differentiate from plausible siblings such as bricscad_query_entities or bricscad_read_attributes, so an agent must infer the boundary.

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?

The phrase 'literal text' implies no regex/wildcard matching, which is a useful selection hint, but there is no explicit when-to-use guidance, no when-not, and no named alternative for broader entity queries. The agent gets no routing help between this tool and the query/attribute siblings.

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