Skip to main content
Glama
BricsCAD MCP

BricsCAD MCP

by alesdev88

bricscad_list_xrefs

Read-only

Lists external references with stored paths and reports whether each referenced file is found, so you can audit drawing dependencies.

Instructions

List external references with their stored path and whether the file was found. 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_xrefs"
  }
}

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.1/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, and the description correctly adds the result cap ('Up to 2000 per call'), which is genuinely useful behavioral context about result volume. It stops short of explaining pagination behaviour (how offset/limit interact with that 2000 cap) or any drawing-state requirement.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences, front-loaded with purpose and followed by the one constraint that matters. Nothing is wasted and there is no filler.

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 described, and the tool is a simple read-only list. Still, with three undocumented parameters and no statement of when the tool applies, the definition is only minimally sufficient for reliable invocation.

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 all three parameters (limit, offset, timeout), so the description carries the full burden and largely fails it. 'Up to 2000 per call' is the only hint at the limit parameter, and only tenuously — it doesn't explain the default of 200, how offset pages through a larger set, or what the timeout governs.

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 external references') and adds the two payload fields an agent cares about: the stored path and whether the referenced file was found. The resource is distinct from the other list_* siblings (blocks, layers, layouts, versions), so an agent can route to it without opening the schema.

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 or when-not-to-use guidance, no mention of prerequisites (an open drawing, a loaded document), and no reference to any alternative tool. The agent must infer the context entirely from the tool name.

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