Mendix Context Bridge
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 |
|---|---|
| list_local_modulesB | Geeft een overzicht van alle modules in het geopende .mpr bestand. |
| inspect_local_microflowC | Zoekt een microflow op naam en geeft de logische stappen terug. |
| get_domain_modelB | Geeft een overzicht van alle entiteiten en types in een specifieke module. |
| inspect_database_schemaB | Geeft de kolomstructuur van een tabel in de lokale database terug. Handig om te begrijpen hoe Mendix data opslaat. |
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 4 tools
Each tool has a clearly distinct purpose: get_domain_model covers entities and types in a module, inspect_database_schema focuses on table column structures, inspect_local_microflow handles microflow logic steps, and list_local_modules lists modules in a file. There is no overlap or ambiguity between these functions.
All tool names follow a consistent verb_noun pattern in snake_case, such as get_domain_model, inspect_database_schema, inspect_local_microflow, and list_local_modules. This uniformity makes the set predictable and easy to understand.
With 4 tools, the count is slightly low but reasonable for the server's purpose of providing Mendix context insights. It covers key areas like modules, domain models, database schemas, and microflows, though it might benefit from additional tools for more comprehensive coverage.
The tools cover basic inspection and listing functions for modules, domain models, database schemas, and microflows, but there are notable gaps. For example, there are no tools for creating, updating, or deleting elements, which limits the server to read-only operations and may cause agent failures in workflows requiring modifications.