Skip to main content
Glama
hexpress-mcp

hexpress-mcp

by GaillumXc

Convert File

convert_file

Converts mesh and geometry files between formats such as .spb, .msh, and .cgns, inferring the format from file extensions and returning the exit code with a log tail.

Instructions

Convert between mesh/geometry formats (hexpressfileconvertx86_64.exe).

e.g. .spb -> .msh, .spb.gz -> .cgns ... Formats are inferred from the extensions. Returns returncode 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": {
      "input_file": "<input_file>",
      "output_file": "<output_file>"
    },
    "name": "convert_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeoutNo
input_fileYes
install_dirNo
output_fileYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 does disclose useful behavior: it shells out to an external executable (hexpressfileconvertx86_64.exe), infers formats from extensions, and returns a returncode plus log tail. It omits whether an existing output_file is overwritten, what permissions or installed binary are required, and what happens on partial failure — significant gaps for a process-launching 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?

Two short sentences plus an example line, with purpose front-loaded and no filler. The parenthetical executable name is slightly noisy but does convey the underlying binary.

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?

An output schema exists, so return-value detail (returncode, log tail) is supplementary rather than required. However, for a 4-parameter tool with zero schema descriptions, the undefined timeout and install_dir plus the absence of overwrite/failure semantics leave the definition short of complete.

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%, so the description must compensate and only partly does: input_file and output_file semantics are conveyed implicitly via the extension examples. The timeout and install_dir parameters receive no explanation anywhere, leaving half the parameters 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 ('Convert between mesh/geometry formats') and backs it with concrete extension examples (.spb -> .msh, .spb.gz -> .cgns). It does not explicitly distinguish itself from the sibling convert_cad, so an agent must guess whether CAD input belongs here.

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 only implied through example extension pairs and the note that formats are inferred from extensions, which tells the agent how inputs are interpreted. There is no explicit when-to-use vs. convert_cad, no preconditions, and no statement about unsupported format combinations.

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