openmep
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| size_ductA | Recommend a standard round diameter for one duct run carrying a given CFM, with velocity and friction at that size. Optionally grade an existing round, rect, or oval section as ok, undersized, or oversized. |
| size_duct_networkA | Size every supply, return, exhaust, and outside-air segment of a connected duct network. Each terminal's requiredCfm is carried along its shortest same-system path to equipment and summed per segment; roles (main/branch/runout) are inferred. Sizes at the fixed default friction rate, or, when fan is given with segment lengthFt and fitting equivalentLengthFt, at the Manual D friction rate derived from available static pressure over the total effective length (returned as design: ASP, TEL, friction rate, longest paths). Returns per-segment recommendations, grades for segments with an existing section, and findings: missing-required-cfm, no-equipment-path, dangling-reference, mixed-system-segment, undersized, oversized, friction-rate-out-of-range, missing-equivalent-length. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The tools operate at different scopes: size_duct handles a single duct run, while size_duct_network sizes an entire network with multiple segments. The names are similar but the descriptions clearly differentiate their purposes, making confusion unlikely for an agent.
Both tool names follow a consistent verb_noun pattern (size_duct, size_duct_network). The only minor issue is that the noun part is very similar, but the naming convention itself is consistent.
With only 2 tools, the server is quite thin for a duct sizing domain. While each tool is well-scoped, the limited count may force agents to rely on external knowledge for common tasks like equipment selection or duct material properties.
The surface covers core duct sizing operations but lacks obvious complementary tools such as equipment selection, pressure loss calculations for fittings beyond equivalent length, or output formatting. Notably, there is no tool to retrieve or list existing duct networks, which could be a gap for iterative design workflows.