Skip to main content
Glama
BricsCAD MCP

BricsCAD MCP

by alesdev88

bricscad_status

Read-only

Check whether BricsCAD is running, verify how recently its listener reported, and identify the current drawing before issuing control or audit commands.

Instructions

Report whether BricsCAD is running, how recently its listener reported, and the current drawing.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior3/5

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

The readOnlyHint/destructiveHint annotations already establish the safety profile, so the description's main contribution is naming the three reported signals, including listener recency, which is genuinely useful diagnostic context. It does not mention what happens if BricsCAD is down (error vs. a 'not running' status), which is the key behavioral ambiguity for this tool.

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?

A single sentence that front-loads the outcome (running or not) before the supporting details. Every clause carries information and there is no filler.

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?

With an output schema present, return formatting need not be explained, and the annotations cover safety; the description supplies the substance of what is reported. The only gap is the absent guidance on how a 'not running' result surfaces, which matters for a health-check tool an agent will gate other calls on.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. No parameter detail is needed or missing.

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 uses a specific verb ('Report') and enumerates exactly what state is returned: process liveness, listener freshness, and the active drawing. This clearly separates it from siblings like bricscad_start/bricscad_stop, though it never names those siblings explicitly.

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 only implied by the tool's nature as a status check; there is no statement of when to call it (e.g., before other operations to verify connectivity) and no explicit exclusions or alternatives. An agent can infer the intent but is given no routing guidance.

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