Skip to main content
Glama
hexpress-mcp

hexpress-mcp

by GaillumXc

Convert Cad

convert_cad

Re-export a Parasolid CAD file through the HEXPRESS kernel to produce a V32-era transmit the batch mesher can read, preventing 0xC0000005 segfaults on newer files.

Instructions

Re-export a Parasolid CAD file through the HEXPRESS GUI kernel.

hexpresshybridx86_64.exe (batch mesher) can segfault (0xC0000005) reading newer Parasolid transmits that hexpressx86_64.exe imports fine — passing the file through this converter (import + export) produces a byte-level V32-era transmit the batch mesher digests. Also useful to bake/validate any Parasolid .x_t/.x_b before meshing. Output defaults to _v32.X_T next to the input. Returns the exported path.

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": {
      "input_file": "<input_file>"
    },
    "name": "convert_cad"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeoutNo
input_fileYes
install_dirNo
output_fileNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the burden well: it reveals that the conversion runs through the GUI kernel, that output is a byte-level V32-era transmit, the default output path and filename convention, and that the tool returns the exported path. It omits whether a GUI window is opened/blocking, whether an existing output file is overwritten, and what install_dir does.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in a single clear sentence, and the remaining sentences all carry real information (trigger, secondary use, output default, return value). The segfault explanation is dense and em-dash-heavy, making it slower to scan than it needs to be.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The output schema exists and the description confirms the returned path, so return values need no elaboration. Still missing for a tool that spawns an executable: the meaning of install_dir, whether it blocks until the GUI conversion completes, and the timeout parameter's role in that wait.

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

Parameters3/5

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

Schema coverage is 0%, so the description must carry parameter meaning; it explains the input resource and the default output location/name, which is genuinely beyond the schema's 'default: null'. However, two of four parameters (timeout, and especially install_dir) receive no explanation at all.

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 first sentence names a specific verb (re-export) and resource (Parasolid CAD file) and the mechanism (HEXPESS GUI kernel). It is clear what the tool does, though it never distinguishes itself from the sibling convert_file, which plausibly overlaps.

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

Usage Guidelines4/5

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

It gives a concrete trigger — the batch mesher segfaulting (0xC0000005) on newer Parasolid transmits that the GUI binary imports — plus a second general case (bake/validate any .x_t/.x_b before meshing). There are no explicit exclusions and no named alternative such as convert_file, so it stops short of routing guidance.

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