Skip to main content
Glama
cad2revit-mcp

cad2revit-mcp

parse_dwg

Analyzes DXF/DWG drawings to extract layers, text, and frames, then reports health findings so CAD issues are caught before Revit conversion.

Instructions

解析DXF/DWG图纸并做可用性体检,返回图层、文字、图框与健康结论。

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": {
      "file_path": "<file_path>"
    },
    "name": "parse_dwg"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYes
disciplineNostructure
level_nameNo
convert_dwgNo

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 exist, so the description carries the full burden. It discloses the outputs meaningfully and '解析' implies a non-destructive read, but it never addresses the side effects of the convert_dwg flag (default true), whether converted files are written to disk, permission requirements, or how long a large drawing takes to process.

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 compact sentence with no filler, leading with the core action and following with the return payload. It is appropriately sized, though its brevity is partly the cause of the missing parameter and behavior detail.

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 values need not be explained, but the tool has four undocumented parameters, no annotations, and a default that triggers DWG conversion. For that complexity the description is materially incomplete and an agent could not confidently set discipline, level_name, or convert_dwg from it.

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 four parameters, and the description mentions none of them. It says nothing about what file_path accepts, what 'discipline' (default 'structure') controls, what level_name means, or why convert_dwg would be toggled, so it fails to compensate for the coverage gap.

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 ('解析') applied to a specific resource (DXF/DWG drawings) plus a health-check capability, and names the concrete payload (layers, text, frames, health conclusion). An agent can distinguish it from siblings such as check_model or detect_components, though the description never explicitly contrasts itself with them.

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 and no named alternative. The phrase '可用性体检' implies a pre-processing quality check on CAD drawings, but the agent must infer when to pick this over check_model or detect_components.

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