Skip to main content
Glama
hexpress-mcp

hexpress-mcp

by GaillumXc

Generate Conf

generate_conf

Creates a HEXPRESS batch .conf file from geometry inputs, output mesh, refinement levels, boundary conditions, and viscous-layer settings without running the mesh job.

Instructions

Generate a HEXPRESS batch .conf file (without running it).

input_files: geometry/mesh inputs (STL, .spb, .CATPart, .igs ...), absolute paths recommended. output_mesh: output file name, e.g. resultMesh.msh (FNMB mesh) or .spb.gz. base_h: base cell size for the octree mesher. refinements: {selection_name: [initial_level, min_level]} — LOCALREFINEMENTDEFINITION. boundary_conditions: {selection_name: bc_type} — BCDEFINITION (e.g. SOL, INL, OUT, SYM). num_boundary_layers: viscous layer count (NUMBNDLAYERS). s2v_mesh: surface-to-volume (tet-dominant) mode instead of octree hybrid. Returns the written path and the full conf content.

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_files": "<input_files>",
      "output_mesh": "<output_mesh>"
    },
    "name": "generate_conf"
  }
}

Input Schema

NameRequiredDescriptionDefault
base_hNo
s2v_meshNo
conf_nameNo
full_hexaNo
extra_linesNo
input_filesYes
output_meshYes
refinementsNo
exact_meshingNo
mark_all_outerNo
suppress_prefixNo
s2v_surface_onlyNo
boundary_conditionsNo
num_boundary_layersNo
boundary_layer_transitionNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/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 usefully discloses that nothing is executed and that the call returns the written path plus the full conf content, but it does not say where the file is written, whether an existing file is overwritten, what conf_name defaults to, or how failures surface — material behavior for a file-writing tool.

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 a compact parameter glossary, one line per concept, with no filler. The formatting is easy to scan, though the bare list lacks grouping between mesh-shape options and output options.

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?

Placed incorrectly relative to the other names? No — a 15-parameter tool with no annotations and an existing output schema needs exactly this: a clear purpose, the not-executed caveat, and per-parameter meaning. The remaining gaps are limited to booleans whose names are largely self-descriptive (full_hexa, s2v_surface_only), and return values are covered by the output schema.

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 description coverage is 0%, so the description is the only documentation, and it meaningfully explains 8 parameters, including the underlying conf keywords (LOCALREFINEMENTDEFINITION, BCDEFINITION, NUMBNDLAYERS) and the refinement tuple shape [initial_level, min_level]. However, 7 parameters — conf_name, full_hexa, extra_lines, exact_meshing, mark_all_outer, suppress_prefix, s2v_surface_only, boundary_layer_transition — receive no explanation at all, leaving roughly half the surface undocumented.

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?

The first sentence names a specific verb and artifact — 'Generate a HEXPRESS batch .conf file' — and the clause '(without running it)' immediately separates it from the run/execute siblings such as run_mesh and run_script. An agent can identify the tool's job without opening the schema.

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?

The parenthetical 'without running it' establishes the key usage context: this produces the script, not the mesh, implying launch/run tools handle execution. It stops short of explicitly naming run_mesh or run_script as the follow-up step, so no explicit alternative or exclusion is stated.

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