Skip to main content
Glama
hexpress-mcp

hexpress-mcp

by GaillumXc

Get Status

get_status

Checks HEXPRESS install paths, executables, license server state, GUI status, and platform notes so you can verify the environment before running mesh generation.

Instructions

Probe the environment: HEXPRESS install paths, executables, license server state, whether the GUI is running, and platform notes. Call first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
install_dirNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. "Probe" implies a read-only diagnostic with no side effects, but that is inference rather than disclosure, and nothing is said about permissions, cost, whether results are cached, or how failures surface. It adds useful scoping but leaves core behavioral traits implicit.

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?

Two compact sentences, front-loaded with the resource list and ending in an actionable directive. No redundant phrasing or restatement of the tool name.

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

Completeness4/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 values need not be described, and the tool itself is a simple no-required-param probe. The only real gap is the unexplained optional install_dir parameter, which matters more here because it is the tool's sole input.

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?

There is one optional parameter, install_dir, with 0% schema description coverage, and the description does not mention it at all. An agent cannot tell whether install_dir overrides auto-detection, what format it takes, or what happens when it is omitted, so the description fails to compensate for the schema gap.

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 description names a specific verb ("Probe") plus an enumerated set of environment facts: HEXPRESS install paths, executables, license server state, GUI running status, and platform notes. That enumeration cleanly separates it from the siblings (convert_cad, run_mesh, launch_gui), which do work rather than report state.

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?

"Call first" gives an explicit ordering directive, implying this is a prerequisite/environment-check before conversion, meshing, or GUI launch. It does not state when NOT to call it or what to do if the probe fails, so it falls short of full when/when-not guidance.

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