Fragment MCP Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| convert-ifc-to-fragC | Convert an IFC file to a .frag file. Needs file-system server |
| load-fragC | Load a .frag file. Needs file-system server |
| fetch-elements-of-categoryC | Fetch elements of a specified category |
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 3 tools
Each tool has a clearly distinct purpose: converting IFC to FRAG, fetching elements by category, and loading FRAG files. There is no overlap or ambiguity in their functions, making it easy for an agent to select the correct tool for each task.
The tools follow a consistent verb-object naming pattern (e.g., convert-ifc-to-frag, fetch-elements-of-category, load-frag), with all names using kebab-case. There is a minor deviation in 'load-frag' being slightly simpler, but overall the naming is predictable and readable.
With only 3 tools, the server feels thin for a domain involving IFC/FRAG file processing and element fetching. While the tools cover basic operations, the scope suggests more comprehensive functionality might be expected, such as querying or manipulating loaded data.
The toolset has significant gaps for a fragment processing domain. It lacks operations for updating, deleting, or querying beyond category fetching, and there are no tools for saving or exporting modified fragments, leaving agents with dead ends in workflows.