Skip to main content
Glama
cad2revit-mcp

cad2revit-mcp

check_model

Compares a generated BIM model with the original CAD drawing to identify missed elements, misalignments, missing parameters, duplicate components, and topology errors for correction.

Instructions

模型与原图比对,输出漏识别、错位、参数缺失、重复构件与拓扑异常。

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": {
      "task_id": "<task_id>"
    },
    "name": "check_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
checksNo
task_idYes
tolerance_mmNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does useful work by disclosing the five output categories the check produces, which tells the agent what kind of result to expect. However it never states whether the operation is read-only or mutating, what permissions or preconditions are required, or how tolerance_mm affects the findings.

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?

A single front-loaded sentence naming the core action first, then the outputs. No filler and nothing redundant. It is terse to the point that supporting detail (params, preconditions) is absent, but the sentence itself is well constructed.

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?

The output schema covers return values, so the description needn't explain the response shape. But for a 3-parameter tool with zero schema documentation and no annotations, the description omits everything an agent needs to call it correctly: what task_id references, what tolerance_mm controls, and what values 'checks' accepts.

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 three parameters, so the description must compensate and largely fails to. The listed check categories loosely hint at what 'checks' might accept, but the required task_id and tolerance_mm (default 50) are never explained — the agent gets no meaning for the tolerance or the source of the task id.

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-resource pairing: compare the model (模型) against the original drawing (原图). It goes on to enumerate the exact findings it emits (missed detections, misalignment, missing parameters, duplicate components, topological anomalies). This is enough to distinguish it from detect_components and query_graph, though it doesn't explicitly name any sibling.

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?

No when-to-use guidance. There is no mention of prerequisites (e.g. a prior parse_dwg/query_graph step producing task_id), no 'use this instead of X when Y', and no when-not-to-use exclusions. The comparison framing implies a QA/validation context but the agent must infer it.

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