Skip to main content
Glama
hexpress-mcp

hexpress-mcp

by GaillumXc

Run Mesh

run_mesh

Run HEXPRESS on a .conf file to generate a mesh in batch with optional MPI process count and timeout control.

Instructions

Run hexpresshybridx86_64.exe on a .conf file (generate a mesh in batch).

conf_file: path returned by generate_conf (or any HEXPRESS-exported conf). np: number of MPI processes (>1 adds -ompi -np N). timeout: seconds before the run is killed (default 1 h; big meshes need more). Returns returncode, elapsed time, output file info and the log tail.

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": {
      "conf_file": "<conf_file>"
    },
    "name": "run_mesh"
  }
}

Input Schema

NameRequiredDescriptionDefault
npNo
timeoutNo
conf_fileYes
install_dirNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.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 burden and does well: it discloses that an external executable is launched, that np>1 appends '-ompi -np N', that timeout kills the run, and that returncode/elapsed/output/log tail come back. It does not say whether existing output files are overwritten or what a nonzero returncode implies.

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 with the core action, then one terse line per parameter; nothing is padded. The closing 'Returns ...' line is largely redundant with the existing output schema, which is the only wasted text.

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?

For a tool that launches an external binary with MPI and a kill timer, the description covers the operational essentials and the output schema covers return values. The undocumented install_dir parameter and the absence of any failure-mode or overwrite semantics leave a real gap.

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 must compensate. It does for three of four parameters — conf_file's expected provenance, np's effect on the command line, timeout's default and 'big meshes need more' guidance — but install_dir is never mentioned and remains opaque.

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 concrete verb and resource: run hexpresshybridx86_64.exe on a .conf file, with the clarifying parenthetical '(generate a mesh in batch)'. That distinguishes it from generate_conf and convert_cad, though the boundary with the sibling run_script is left implicit.

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

Usage Guidelines3/5

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

Usage is implied through the note that conf_file is 'path returned by generate_conf', which sketches the intended pipeline, and the np/timeout notes hint at when to tune. There is no explicit when-to-use versus run_script or launch_gui, and no stated prerequisites such as needing a prior generate_conf call.

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