multiCAD-mcp-server

Overview Schema Source Related Servers Discussions Admin

export_ce3x_envelope

Extract CAD thermal envelope parameters for CE3X energy certification, including wall areas, orientations, windows, and floor area, then save them as a standardized JSON file.

Instructions

Extract CAD thermal building envelope parameters for CE3X energy certification.

Behavior:

Mutation: Strictly read-only for CAD geometry; does not alter drawing database or active viewport.
Persistence: Saves a standardized JSON envelope file to the configured output directory.
Side Effects: Filesystem write of the output JSON file.

Usage Guidelines:

When to Use: Call when bridging CAD floor plans to energy certification workflows (CE3X-MCP-SERVER, CTE DB-HE, or RD 390/2021). Computes exterior wall surface areas, wall azimuth orientations (N, S, E, W) by normal vector geometry, associated window openings, and usable floor area.
Sibling Routing / Alternatives:
- For generic drawing takeoffs, Excel spreadsheets, or FIEBDC-3 budgets, use export_data.
- For spatial queries or room area schedules without thermal calculations, use inspect_drawing or manage_entities(operations="area|...").

Parameters:

wall_height: Clear floor-to-ceiling height in meters. Default: 2.70.
climate_zone: CTE climate zone (e.g., "A3", "C1", "D3"). Default: "C1".
building_type: Building typology ("vivienda_individual", "bloque_viviendas", "terciario"). Default: "vivienda_individual".
filename: Output JSON filename. Default: "envolvente_ce3x.json".

Returns: JSON string containing CTE thermal envelope parameters, ready for direct ingestion by CE3X-MCP-SERVER.

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

Input Schema

Name	Required	Default
`filename`	No	envolvente_ce3x.json
`wall_height`	No
`climate_zone`	No	C1
`building_type`	No	vivienda_individual

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 20, 2026

TDQS

A4.6/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it declares read-only CAD behavior, states that it persists a standardized JSON file to the configured output directory, and flags the filesystem-write side effect explicitly. It omits overwrite/collision behavior, permissions, and error handling, which keeps it short of a 5.

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?

Front-loaded purpose sentence followed by clearly labeled Behavior, Usage Guidelines, Parameters, and Returns sections. Well organized and mostly tight, though the Returns paragraph partially duplicates what the output schema already conveys.

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

Completeness5/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 explanation is not required, yet the description still adds mutation/persistence/side-effect context and full parameter semantics. Together with the sibling routing, an agent has everything needed to invoke it correctly.

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?

Schema description coverage is 0%, so the description must compensate, and it documents all four parameters with units ('floor-to-ceiling height in meters'), valid CTE climate zone examples ('A3', 'C1', 'D3'), and building typology values ('vivienda_individual', 'bloque_viviendas', 'terciario') that are not represented as schema enums. Defaults are restated from the schema, which slightly duplicates structured data.

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 (Extract) and resource (CAD thermal building envelope parameters) with the intended domain (CE3X energy certification). It also names the sibling tools (export_data, inspect_drawing, manage_entities) it should not be confused with, so the agent can route correctly without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides an explicit 'When to Use' condition (bridging CAD floor plans to CE3X/CTE DB-HE/RD 390 workflows) and an explicit 'Sibling Routing' block that names alternatives and the conditions selecting them (export_data for generic takeoffs, inspect_drawing for spatial queries). Nothing is left to inference.

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

Deploy Server