CONTAM MCP
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 |
|---|---|
| discover_contam_installationA | Use this when you need to confirm where CONTAM is installed and which executables this MCP server can access. |
| list_contam_case_filesC | Use this when you want to find CONTAM project files, result files, or weather files in a directory tree before running a simulation. |
| get_contam_program_helpA | Use this when you want the built-in command-line usage text for a CONTAM executable before deciding which tool or arguments to use. |
| inspect_contam_projectA | Use this when you want a quick structural summary of a CONTAM .prj file before editing or running it. |
| diagnose_contam_projectB | Use this when a CONTAM project fails to run and you want to inspect referenced support files and nearby candidate matches. |
| update_contam_project_referencesC | Use this when you need to edit the referenced weather, contaminant, or library files inside a CONTAM .prj file. |
| start_contam_bridge_sessionB | Use this when you want to launch ContamX in bridge mode and keep an interactive socket session open across multiple MCP calls. |
| get_contam_bridge_sessionB | Use this when you want to inspect the metadata or last-known state of an active ContamX bridge session. |
| list_contam_bridge_entitiesB | Use this when you want a concise list of the names and ids available inside an active ContamX bridge session. |
| advance_contam_bridge_sessionC | Use this when you want to send control/weather adjustments to a running bridge session and optionally advance ContamX to a new simulation time. |
| close_contam_bridge_sessionA | Use this when you want to end an active ContamX bridge-mode session and release the spawned process and socket. |
| run_contam_simulationB | Use this when you want to validate or run a CONTAM .prj model with ContamX and collect the generated files. |
| upgrade_contam_projectC | Use this when you need to upgrade an older .prj file to a newer CONTAM project format using prjup. |
| compare_contam_sim_resultsC | Use this when you want to compare two CONTAM .sim result files with simcomp. |
| export_contam_sim_textB | Use this when you need to run simread on a .sim file and you already know the response-script text needed for the interactive prompts. |
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 15 tools
Every tool has a clearly distinct purpose with no ambiguity. The tools cover different aspects of CONTAM workflow (installation discovery, project inspection, simulation running, bridge session management, file operations) with precise action-target pairs that prevent misselection.
All tools follow a consistent verb_noun pattern with 'contam' prefix (e.g., discover_contam_installation, run_contam_simulation). The naming is perfectly predictable throughout the set, using snake_case uniformly with clear action verbs.
15 tools is well-scoped for a CONTAM simulation server, covering installation, project management, simulation execution, bridge sessions, and file operations. Each tool earns its place in the domain without being excessive or insufficient.
The toolset provides complete lifecycle coverage for CONTAM projects: discovery, inspection, updating, running simulations, managing bridge sessions, comparing results, and diagnosing issues. No obvious gaps exist for the stated simulation workflow domain.