Skip to main content
Glama
cad2revit-mcp

cad2revit-mcp

detect_components

Recognizes grids, columns, walls, and beams from 2D structural CAD drawings, then outputs evidence-backed component data, confidence scores, issue lists, and relationships for Revit BIM conversion.

Instructions

识别轴网、柱、墙、梁,输出带证据与置信度的构件IR、疑点清单与构件关系图。

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": "detect_components"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes
rule_setNo
element_typesNo
confidence_thresholdNo

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?

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that outputs include evidence, confidence values, an issue list, and a relationship graph, but it does not state whether the operation is read-only, whether it modifies source data, permission requirements, or runtime cost.

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?

The description is a single front-loaded sentence with no wasted wording. It is compact and states the detection targets before the outputs, though the lack of structure contributes to its under-specification elsewhere.

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-value details need not be fully explained. However, for a four-parameter detection tool with 0% schema description coverage and no annotations, the definition omits parameter meanings, usage guidance, and operational behavior, leaving significant gaps.

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 four parameters. The description mentions detectable element categories, which weakly hints at element_types, and confidence, which hints at confidence_threshold, but it does not explain task_id, rule_set, element_types, or confidence_threshold semantics or formats.

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 names a specific detection verb and the exact resources it detects: 轴网、柱、墙、梁. It also states the outputs (构件IR、疑点清单、构件关系图), so the tool's function is clear, though it does not differentiate itself from siblings such as parse_dwg or query_graph.

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 description gives no explicit guidance on when to use this tool versus parse_dwg, query_graph, resolve_ambiguities, or other siblings. There are no prerequisites, exclusions, or workflow context, so an agent must infer usage from the name and description alone.

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