A computerized method for parsing, verifying and executing the contents of a command script submitted for execution, comprising the steps of: receiving, at a server, a command script including at least one token and written in a scripting language from a remote client application (140, 150, 160); providing a first, rapidly-accessible data store only containing at least one primary function signature definition including a primary function name that is associated with an operational command that does not require data retrieval from one or more databases for completion, and a primary parameter list associated with the primary function name and having zero or more parameter specifications; providing a second data store that is less rapidly-accessible than the first data store, the second data store containing at least one secondary function signature definition including a secondary function name that is associated with a command that requires data retrieval from the one or more databases for completion, and a secondary parameter list associated with the secondary function name and having zero or more parameter specifications; recognizing at least one portion of the at least one token to potentially represent a reference to a previously defined function in the scripting language, the potential function reference having a potential function name and zero or more potential parameters associated therewith; searching the first data store for a matching primary function signature definition having a primary function name matching the potential function name and wherein each of the potential parameters has a matching entry in the primary parameter list associated with the same primary function signature definition; searching the second data store for a matching secondary function signature definition having a secondary function name matching the potential function name and wherein each of the potential parameters has a matching entry in the secondary parameter list associated with the same secondary function signature definition, when a matching primary function signature definition is not found in the first data store; executing a function having a function name determined to match the potential function name, thereby creating a result set; and transmitting the result set to the client application. receiving, at a server, a command script including at least one token and written in a scripting language from a remote client application (140, 150, 160); providing a first, rapidly-accessible data store only containing at least one primary function signature definition including a primary function name that is associated with an operational command that does not require data retrieval from one or more databases for completion, and a primary parameter list associated with the primary function name and having zero or more parameter specifications; providing a second data store that is less rapidly-accessible than the first data store, the second data store containing at least one secondary function signature definition including a secondary function name that is associated with a command that requires data retrieval from the one or more databases for completion, and a secondary parameter list associated with the secondary function name and having zero or more parameter specifications; recognizing at least one portion of the at least one token to potentially represent a reference to a previously defined function in the scripting language, the potential function reference having a potential function name and zero or more potential parameters associated therewith; searching the first data store for a matching primary function signature definition having a primary function name matching the potential function name and wherein each of the potential parameters has a matching entry in the primary parameter list associated with the same primary function signature definition; searching the second data store for a matching secondary function signature definition having a secondary function name matching the potential function name and wherein each of the potential parameters has a matching entry in the secondary parameter list associated with the same secondary function signature definition, when a matching primary function signature definition is not found in the first data store; executing a function having a function name determined to match the potential function name, thereby creating a result set; and transmitting the result set to the client application.