Skip to main content
Glama
EGorsel

Mendix Context Bridge

by EGorsel

list_local_modules

Lists all modules in the currently opened Mendix project file to help AI agents understand the project structure without requiring cloud access.

Instructions

Geeft een overzicht van alle modules in het geopende .mpr bestand.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler logic for the 'list_local_modules' tool. Checks the tool name, calls reader.getModules() to fetch modules, and returns the JSON-stringified result as text content.
    if (request.params.name === "list_local_modules") {
        const modules = reader.getModules();
        return {
            content: [{ type: "text", text: JSON.stringify(modules, null, 2) }]
        };
    }
  • src/server.ts:46-52 (registration)
    Registration of the 'list_local_modules' tool in the ListTools response, including its name, Dutch description, and empty input schema (no parameters required).
    {
        name: "list_local_modules",
        description: "Geeft een overzicht van alle modules in het geopende .mpr bestand.",
        inputSchema: {
            type: "object",
            properties: {}
        }
  • Input schema for 'list_local_modules': an empty object, indicating no input parameters are needed.
    inputSchema: {
        type: "object",
        properties: {}
    }
  • Core helper method in MprReader class that implements the module listing logic: queries the SQLite database (.mpr file) for distinct 'containerId' from 'Unit' table, handling errors and returning a list of module identifiers.
    getModules(): string[] {
        if (!this.db) {
            throw new Error('Database not connected.');
        }
        try {
            // Placeholder: In a real Mendix DB, modules might be units with specific types 
            // or folders. We will return generic names or 'Unknown' if we can't determine.
            // Attempting to select distinct container IDs or similar if they represent modules.
    
            // For now, returning a mock list mixed with whatever we find in Unit to show activity.
            const stmt = this.db.prepare("SELECT DISTINCT containerId FROM Unit LIMIT 50");
            const rows = stmt.all() as any[];
            return rows.map(r => r.containerId || "Unidentified_Module");
        } catch (error) {
            console.error('Error getting modules:', error);
            return [];
        }
    }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool provides an overview but doesn't describe what 'overzicht' entails (e.g., list format, metadata included), whether it's read-only or has side effects, or any constraints like performance or file access requirements. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, clear sentence in Dutch that directly states the tool's function without unnecessary words. It's front-loaded with the core purpose and appropriately sized for a simple tool with no parameters.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate. It states what the tool does but lacks details on output format, behavioral traits, or usage context. Without annotations or output schema, the description should ideally provide more context about what 'overzicht' includes, but it's complete enough for basic understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, and schema description coverage is 100% (empty schema). The description doesn't need to add parameter information, so it meets the baseline of 4 for tools with no parameters, as there's no gap to compensate for.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Geeft een overzicht van alle modules in het geopende .mpr bestand' (Provides an overview of all modules in the opened .mpr file). It specifies the verb ('geeft een overzicht' - provides an overview) and resource ('modules in het geopende .mpr bestand'), though it doesn't explicitly differentiate from sibling tools like 'get_domain_model' or 'inspect_local_microflow'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an opened .mpr file), exclusions, or comparisons to sibling tools like 'inspect_local_microflow' which might handle microflows within modules. Usage is implied by the resource scope but not explicitly stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/EGorsel/mendix-local-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server