MCP Server for Alloy Modeling Language
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 |
|---|---|
| execute_alloyC | Execute Alloy modeling language code and return structured JSON results |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| create_alloy_model | Generate an Alloy model based on a system description |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| alloy-docs | |
| alloy-examples |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools, making disambiguation perfect.
The single tool follows a clear verb_noun pattern (execute_alloy), and with no other tools, consistency is inherently perfect.
One tool is too few for a modeling language server, as it lacks essential operations like model validation, instance generation, or visualization, making the scope feel incomplete.
The tool surface is severely incomplete; it only allows code execution without supporting core Alloy workflows such as checking assertions, generating examples, or analyzing models, leading to significant gaps.