Loading ToolBench
Model Context Protocol server for Ansys Mechanical engineering simulation software, enabling remote control of Mechanical instances running on Windows VMs via gRPC
Five tools with READ_ONLY risk profile. All have descriptions (10-60 chars, below baseline 194 avg), but critically, NO input schemas are visible in the provided source code. The `search` tool accepts query, manual, rows parameters but no JSON Schema is shown. The `read` tool accepts doc_ids (array) and max_chars (integer) but schema is not declared. Without visible schemas, per-rule, schema scores must be 0. Tool names are action verbs (search, read, list, manuals, versions, products), good naming. However, descriptions are terse (e.g., 'full-text search, prints ids to read' is 34 chars, below the 50-200 char LLM-optimized range). Parameter descriptions are absent from the visible interface. Error handling is not documented. No output schema is specified.
list available manuals for the configured product and version
list available Ansys products in the documentation
print one or more pages as plain text
full-text search, prints ids to read
list available Ansys releases in the documentation
No input schemas visible in source code. All five tools lack JSON Schema definitions with type and description for parameters.
Descriptions are terse (25 - 35 chars) and lack LLM-optimized context. Baseline is 194 chars. No explanation of WHEN to use each tool or what it returns.
Parameter descriptions are missing. 'query', 'manual', 'rows', 'doc_ids', 'max_chars' have no descriptions visible. LLMs cannot infer parameter meaning from names alone.
No output schema documented. LLMs do not know what fields to expect from search(), read(), manuals(), versions(), or products() responses.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 44 | 2026-07-28+ | v2 |
No error handling guidance. If ansyshelp endpoint fails or returns 404, no recovery instructions are provided to the LLM.