Skip to main content
Glama
BricsCAD MCP

BricsCAD MCP

by alesdev88

bricscad_start

Launches BricsCAD in a separate window and connects to it for MCP control, refusing to start if the requested version is already running.

Instructions

Start BricsCAD in its own window and connect to it. Refuses if that version is already running.

version: for example "26". Defaults to BRICSCAD_VERSION, then the newest installed.

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

Input Schema

NameRequiredDescriptionDefault
versionNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes beyond the supplied annotations (readOnlyHint=false, destructiveHint=false) by disclosing that this launches an external application in its own window, establishes a connection, and errors out if the version is already running. It stops short of saying whether it blocks, how long startup takes, or what happens to an existing connection.

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 short lines with the core action first, the refusal condition second, and parameter detail last. No filler sentences.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A simple one-parameter launch tool with an output schema, so return-value detail is not needed. The main action and failure mode are covered; whether the call blocks and how long it takes is the only notable omission.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the load and does so: it gives an example value ('26') and the full default resolution chain (BRICSCAD_VERSION env var, then newest installed). Without this text the lone parameter would be undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Start BricsCAD in its own window and connect to it') plus a concrete failure condition. An agent can distinguish this from bricscad_status/bricscad_stop/bricscad_list_versions without inspecting schemas.

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?

The scenario is implied by the verb, and 'Refuses if that version is already running' effectively warns the agent to check state first, but no sibling is named and no explicit precondition sequence (e.g. list_versions → start) is given.

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