Skip to main content
Glama
hexpress-mcp

hexpress-mcp

by GaillumXc

Inspect Geometry

inspect_geometry

Reports the selection names a geometry file will produce for BCDEFINITION/LOCALREFINEMENTDEFINITION batch conf, reading STL solid names and flagging binary STLs with empty names.

Instructions

Report the selection names a geometry file will produce for BCDEFINITION / LOCALREFINEMENTDEFINITION in a batch conf.

For .stl: reads the solid names directly (hexpresshybridx86_64 groups triangles by STL solid name — import_mode 2, the default). Empty-string names mean a binary STL (no names stored) — use feature grouping (import_mode 1) there and discover TMP-style names from the mesh log. For .spb/.igg project files the names live inside the project; open it in the GUI once or query via run_script. Non-STL inputs raise an error.

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

Input Schema

NameRequiredDescriptionDefault
timeoutNo
input_fileYes
import_modeNo
install_dirNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/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 disclose real behavior: the default import_mode of 2, the meaning of empty-string solid names, the workaround of discovering TMP-style names from the mesh log, and that unsupported inputs error out. It does not mention runtime cost, the timeout's effect, or what the returned selection names look like as a payload.

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

Conciseness5/5

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

The core purpose is front-loaded in one sentence, then format-specific caveats follow in a compact, scannable sequence. No filler phrasing; every clause adds a decision-relevant fact.

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-shape explanation is rightly omitted, and the format guidance is unusually rich. But the unresolved .spb/.igg versus 'non-STL errors' conflict and the silent timeout/install_dir parameters leave an agent without enough to invoke this reliably for anything but plain STL input.

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 explain all four parameters; it meaningfully explains import_mode (default 2, vs. 1 for feature grouping) and implies what input_file must be. timeout and install_dir get no treatment at all, leaving half the parameters undocumented anywhere.

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 and resource: report the selection names a geometry file produces for BCDEFINITION / LOCALREFINEMENTDEFINITION in a batch conf. That is concrete enough to distinguish it from run_script, which it explicitly names as the alternative path for project files.

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?

Gives format-conditional guidance (.stl reads solid names; binary STL yields empty strings, so switch to import_mode 1; .spb/.igg names live inside the project, so use the GUI or run_script) plus a failure mode for non-STL inputs. The only weakness is that the .spb/.igg paragraph and the closing 'Non-STL inputs raise an error' sit in tension, leaving the agent unsure whether project files are supported at all.

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